Hi Chinna and Lynn
As you requested I've started a new thread on the User list to address
your concerns
http://groups.google.com/group/hudson-users/browse_thread/thread/e5732d1a6f6c03d5
In essence, even after the fork, your current Hudson installations
will not be
affected. The Hudson project will continue to be developed and
supported after the fork. Your current installation will run fine,
and you won't need to change any code. How the fork will effect you
moving forward is you can now go to either hudson-ci.org or jenkins-
ci.org to get your distribution and plugins. It is unclear as to how
these two distributions will differ in the short-term, but that is
something that you can follow.
After KK, Andrew and co. rename the mailing lists and github
repository to Jenkins, Hudson will start using the java.net mailing
lists (which are still in place from November), and we have a mirror
of the github repository (in git) on the hudson.java.net that will
become the primary after the Jenkins fork. We can look into moving
this back to github after we re-create the Hudson project if that
makes it easier on people. Please let me know if you have any other
questions or concerns.
Susan
I was hopeful that maybe both camps could play nicely (so each party
gains something from the other) but it seems that we are going to have
two competing products out there in the market just to add to
confusion to those new to Hudson/Jenkins :(
Richard.