The vote is closed, and the results are in. More than half of the total votes were from ineligible voters, but the result would have been the same either way. The final result of all eligible votes is as follows: 214 votes to rename, and 14 for the status quo. You can see the individual votes at https://groups.google.com/group/hudson-jenkins-vote.
So what does this mean now? Well, it means Jenkins lives. We've registered jenkins-ci.org, though it's empty at the moment. In the coming days, we will be renaming the existing Google Groups to jenkins-*@googlegroups.com, renaming the Twitter account from @hudsonci to @jenkinsci, and renaming our organization at Github from hudson to jenkinsci. I wanted to make sure everyone had notice ahead of time that this was happening, so that no one gets surprised by changes to their incoming mail, etc. As said before, the initial, interim governance board will consist of me, Kohsuke and, if he and Oracle are willing, Winston. If Winston is unwilling or unable to continue in that role with Jenkins, we will select a replacement interim member. The interim board will work on the details of a more permanent governance process going forward. Discussions on the infrastructure changes (including things like the Maven groupId/artifactIds, etc) will be in public, on these lists. We're working to get the JIRA and wiki contents migrated over to the Jenkins site, and hope to work with Oracle to get that done in the next couple days.
Putting aside logistics, I want to personally thank everyone for voting, and especially thank everyone who voted for renaming for supporting the Jenkins project and its future. Jenkins is not Oracle's project, nor CloudBee's project, nor my project, nor Kohsuke's project - it's the community's project, and it's going to thrive.
I've been informed that Winston will not be taking the seat, so I'd like to announce that Dean Yu of Yahoo, a longtime Hudson contributor and major user, will be taking the third seat on the interim board.
A.
On Sat, Jan 29, 2011 at 12:22 PM, Andrew Bayer <andrew.ba...@gmail.com>wrote:
> The vote is closed, and the results are in. More than half of the total > votes were from ineligible voters, but the result would have been the same > either way. The final result of all eligible votes is as follows: 214 votes > to rename, and 14 for the status quo. You can see the individual votes at > https://groups.google.com/group/hudson-jenkins-vote.
> So what does this mean now? Well, it means Jenkins lives. We've registered > jenkins-ci.org, though it's empty at the moment. In the coming days, we > will be renaming the existing Google Groups to jenkins-*@googlegroups.com, > renaming the Twitter account from @hudsonci to @jenkinsci, and renaming our > organization at Github from hudson to jenkinsci. I wanted to make sure > everyone had notice ahead of time that this was happening, so that no one > gets surprised by changes to their incoming mail, etc. As said before, the > initial, interim governance board will consist of me, Kohsuke and, if he and > Oracle are willing, Winston. If Winston is unwilling or unable to continue > in that role with Jenkins, we will select a replacement interim member. The > interim board will work on the details of a more permanent governance > process going forward. Discussions on the infrastructure changes (including > things like the Maven groupId/artifactIds, etc) will be in public, on these > lists. We're working to get the JIRA and wiki contents migrated over to the > Jenkins site, and hope to work with Oracle to get that done in the next > couple days.
> Putting aside logistics, I want to personally thank everyone for voting, > and especially thank everyone who voted for renaming for supporting the > Jenkins project and its future. Jenkins is not Oracle's project, nor > CloudBee's project, nor my project, nor Kohsuke's project - it's the > community's project, and it's going to thrive.
On Sun, Jan 30, 2011 at 7:22 AM, Andrew Bayer <andrew.ba...@gmail.com> wrote: > Hi all - > The vote is closed, and the results are in. More than half of the total > votes were from ineligible voters, but the result would have been the same > either way. The final result of all eligible votes is as follows: 214 votes
Invisible userbases, gotta love 'em - even if ineligible ;-).
> to rename, and 14 for the status quo. You can see the individual votes > at�https://groups.google.com/group/hudson-jenkins-vote. > So what does this mean now? Well, it means Jenkins lives. We've registered
Excellent, congratulations to the Jenkins team! I will let my friends and colleagues know.
-- Kamal
-- By three methods we may learn wisdom: First, by reflection, which is noblest; Second, by imitation, which is easiest; and third by experience, which is the bitterest. -- Confucius
Thanks for informing all developments around the re-naming. Could someone compile what it really mean to existing Hudson installations core as well as plug ins.
On Saturday, January 29, 2011, Kamal Advani <kamal.adv...@gmail.com> wrote: > On Sun, Jan 30, 2011 at 7:22 AM, Andrew Bayer <andrew.ba...@gmail.com> wrote: >> Hi all - >> The vote is closed, and the results are in. More than half of the total >> votes were from ineligible voters, but the result would have been the same >> either way. The final result of all eligible votes is as follows: 214 votes
> Invisible userbases, gotta love 'em - even if ineligible ;-).
>> to rename, and 14 for the status quo. You can see the individual votes >> at�https://groups.google.com/group/hudson-jenkins-vote. >> So what does this mean now? Well, it means Jenkins lives. We've registered
> Excellent, congratulations to the Jenkins team! I will let my friends > and colleagues know.
> -- Kamal
> -- > By three methods we may learn wisdom: First, by reflection, which is > noblest; Second, by imitation, which is easiest; and third by > experience, which is the bitterest. > -- Confucius
> Thanks for informing all developments around the re-naming. Could > someone compile what it really mean to existing Hudson installations > core as well as plug ins.
> -chinna
> On Saturday, January 29, 2011, Kamal Advani <kamal.adv...@gmail.com> wrote: >> On Sun, Jan 30, 2011 at 7:22 AM, Andrew Bayer <andrew.ba...@gmail.com> wrote: >>> Hi all - >>> The vote is closed, and the results are in. More than half of the total >>> votes were from ineligible voters, but the result would have been the same >>> either way. The final result of all eligible votes is as follows: 214 votes
>> Invisible userbases, gotta love 'em - even if ineligible ;-).
>>> to rename, and 14 for the status quo. You can see the individual votes >>> at https://groups.google.com/group/hudson-jenkins-vote. >>> So what does this mean now? Well, it means Jenkins lives. We've registered
>> Excellent, congratulations to the Jenkins team! I will let my friends >> and colleagues know.
>> -- Kamal
>> -- >> By three methods we may learn wisdom: First, by reflection, which is >> noblest; Second, by imitation, which is easiest; and third by >> experience, which is the bitterest. >> -- Confucius
There should be very little to be concerned about. With Kohsuke and team in charge again (yeah!!), the emphasis is always on ease of install/upgrade/transition. However, there will be some time spent for the various public / infrastructure pieces to get transitioned, as noted by Andrew.
I don't know about other mostly-inactive devs like myself, but I'm excited about the move, and am looking forward to working again under the new banner. I do need to get my plugin moved over to github, don't I...
>> Thanks for informing all developments around the re-naming. Could >> someone compile what it really mean to existing Hudson installations >> core as well as plug ins.
>> -chinna
>> On Saturday, January 29, 2011, Kamal Advani <kamal.adv...@gmail.com> >> wrote: >>> On Sun, Jan 30, 2011 at 7:22 AM, Andrew Bayer <andrew.ba...@gmail.com> >>> wrote: >>>> Hi all - >>>> The vote is closed, and the results are in. More than half of the total >>>> votes were from ineligible voters, but the result would have been the >>>> same >>>> either way. The final result of all eligible votes is as follows: 214 >>>> votes
>>> Invisible userbases, gotta love 'em - even if ineligible ;-).
>>>> to rename, and 14 for the status quo. You can see the individual votes >>>> at�https://groups.google.com/group/hudson-jenkins-vote. >>>> So what does this mean now? Well, it means Jenkins lives. We've >>>> registered
>>> Excellent, congratulations to the Jenkins team! I will let my friends >>> and colleagues know.
>>> -- Kamal
>>> -- >>> By three methods we may learn wisdom: First, by reflection, which is >>> noblest; Second, by imitation, which is easiest; and third by >>> experience, which is the bitterest. >>> -- Confucius
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.
As Scott has said, the development will continue under a new banner, so there should be very little to worry about.
Right now, we are working parallel on both the infrastructure migration front and the first Jenkins release front, and some of this needs to be coordinated. So please give us some time to get our acts together.
> Thanks for informing all developments around the re-naming. Could > someone compile what it really mean to existing Hudson installations > core as well as plug ins.
> -chinna
> On Saturday, January 29, 2011, Kamal Advani<kamal.adv...@gmail.com> wrote: >> On Sun, Jan 30, 2011 at 7:22 AM, Andrew Bayer<andrew.ba...@gmail.com> wrote: >>> Hi all - >>> The vote is closed, and the results are in. More than half of the total >>> votes were from ineligible voters, but the result would have been the same >>> either way. The final result of all eligible votes is as follows: 214 votes
>> Invisible userbases, gotta love 'em - even if ineligible ;-).
>>> to rename, and 14 for the status quo. You can see the individual votes >>> at https://groups.google.com/group/hudson-jenkins-vote. >>> So what does this mean now? Well, it means Jenkins lives. We've registered
>> Excellent, congratulations to the Jenkins team! I will let my friends >> and colleagues know.
>> -- Kamal
>> -- >> By three methods we may learn wisdom: First, by reflection, which is >> noblest; Second, by imitation, which is easiest; and third by >> experience, which is the bitterest. >> -- Confucius
|
