|Kohsuke Kawaguchi||Oct 2, 2009 2:03 pm|
|Stephen Connolly||Oct 2, 2009 2:22 pm|
|Andrew Bayer||Oct 2, 2009 2:33 pm|
|Kohsuke Kawaguchi||Oct 2, 2009 2:41 pm|
|Dean Yu||Oct 2, 2009 2:50 pm|
|Kohsuke Kawaguchi||Oct 2, 2009 3:02 pm|
|Alan Harder||Oct 2, 2009 3:09 pm|
|Stephen Connolly||Oct 2, 2009 3:16 pm|
|Frederic Jean||Oct 2, 2009 3:26 pm|
|Kohsuke Kawaguchi||Oct 2, 2009 3:36 pm|
|Kohsuke Kawaguchi||Oct 2, 2009 3:45 pm|
|Andrew Bayer||Oct 2, 2009 3:57 pm|
|R. Tyler Ballance||Oct 2, 2009 3:59 pm|
|Jason Chaffee||Oct 2, 2009 4:18 pm|
|Kohsuke Kawaguchi||Oct 2, 2009 4:30 pm|
|Jorg Heymans||Oct 3, 2009 5:25 am|
|Joti||Oct 3, 2009 6:40 am|
|Joti||Oct 3, 2009 6:41 am|
|Jorg Heymans||Oct 4, 2009 12:58 pm|
|Benson Margulies||Oct 4, 2009 3:25 pm|
|Stephen Connolly||Oct 4, 2009 11:48 pm|
|Olivier Lamy||Oct 5, 2009 12:17 am|
|Jorg Heymans||Oct 5, 2009 12:31 am|
|Jorg Heymans||Oct 5, 2009 12:37 am|
|Benson Margulies||Oct 5, 2009 3:53 am|
|Stephen Connolly||Oct 5, 2009 7:43 am|
|Michael Donohue||Oct 5, 2009 8:05 am|
|Edelson, Justin||Oct 5, 2009 8:40 am|
|Jason van Zyl||Oct 5, 2009 8:44 am|
|Kohsuke Kawaguchi||Oct 5, 2009 9:48 am|
|Kohsuke Kawaguchi||Oct 5, 2009 9:54 am|
|Andrew Bayer||Oct 5, 2009 1:06 pm|
|Benson Margulies||Oct 5, 2009 1:53 pm|
|Stephen Connolly||Oct 5, 2009 2:46 pm|
|Jorg Heymans||Oct 6, 2009 10:26 am|
|Andrew Bayer||Oct 6, 2009 10:36 am|
|Julien Renaut||Oct 6, 2009 10:50 am|
|Jorg Heymans||Oct 6, 2009 1:26 pm|
|Jorg Heymans||Oct 6, 2009 1:30 pm|
|Edelson, Justin||Oct 6, 2009 1:34 pm|
|Kohsuke Kawaguchi||Oct 6, 2009 2:55 pm|
|Subject:||Re: Migration from java.net|
|From:||Stephen Connolly (step...@gmail.com)|
|Date:||Oct 2, 2009 3:16:25 pm|
Another option might be to consider moving to codehaus.org (if they'd have us... which I suspect they would)
The advantage there is easier sync to maven central
It has a good jira, wiki and subversion as well as webdav based site deployment for the plugins
2009/10/2 Stephen Connolly <step...@gmail.com>
+1 if we can keep the SCM as subversion and keep the subversion history
2009/10/2 Kohsuke Kawaguchi <Kohs...@sun.com>
As we know, lately java.net has been suffering constant performance problems and minor outages. Because of this, the topic of moving the project from java.net has been a recurring topic on this mailing list, dating back at least before JavaOne 2009.
And this week, java.net had the biggest outage ever. It rendered the entire site inaccessible for about 3 days, and the site is still inaccessible to many users in Europe, Latin America, Russia, and Asia, for which we still have no ETA as of this writing.
During this period, plugin downloads and updates were unavailable, new users weren't able to try out Hudson, and committers weren't able to push changes. Furthermore, because of a problematic code in Hudson, this outage rendered Hudson installations in the wild unconfigurable .
What I'm hearing from the Hudson community is that this is just not tolerable. So I think it's time to move off from java.net --- This is putting me into a very hard position, but I think I have no other choice, really.
The hard part is to figure out the migration plan. This is where I invite the community for suggestions and discussions.
As a starting point of the discussion, I suggest the following plan:
- Move Subversion repository to Kenai . I already have a cloned repository (via svnsync), and we know the people who manage Kenai, so they should be able to import it.
- Move the project website to http://hudson-ci.org/ This is a server we own and manage, so we can control the cache related headers and other things.
- Downloads and update center metadata from dlc.sun.com, mirrored from the java.net Maven repository. This is a highly-available clustered servers that Sun uses for everything from Solaris to JDK, NetBeans to OpenOffice.
- Bug tracker to http://issues.hudson-ci.org/ that we run by ourselves.
I think mailing lists can wait, but Kenai would be a natural place if we are to move, given where source code is going.
This proposal involves in us running some services on our own (like we currently do for Wiki), and these services currently run in Sun-owned network. As we discussed some time ago in IRC, I'm working on opening up the access to such servers to the community, so that multiple people will be able to manage those systems.
My track record of keeping Wiki up and running isn't all that great, but OTOH without owning it, we wouldn't have been able to install plugins we wrote and define custom macros. So I think it's worth the trouble.
Finally, the real credit goes to Andrew Bayer for initiating this discussion.
-- Kohsuke Kawaguchi Sun Microsystems http://weblogs.java.net/blog/kohsuke/