Hi devs, As you probably know by now, Hudson has been split in 2: * Jenkins: Kohsuke and all other committers forked and renamed Hudson since there were trademarks issues with Oracle * Hudson: continuing work by Oracle Some more info: http://jenkins-ci.org/content/whos-driving-thing One thing to note is that Sonatype has sided with Oracle: http://www.sonatype.com/people/2011/02/our-focus-on-advancing-hudson-and-ma… Now we need to pick a version: Jenkins or Hudson (community or Oracle). Personally I'm more tempted to follow Jenkins for the time being since: 1) it's the community after all and they're the one who've been doing the work all these past years 2) they're not going to change how jenkins works whereas my understand is that the hudson architecture will be changed (at least that's what Sonatype wants). So in the short period if we want to continue using stable versions the Jenkins path is the safest one. We can then review our choice when Hudson releases new versions. The first official release of Jenkins is out (1.396). See changelog at http://jenkins-ci.org/changelog Since we're using 1.367 it's a good time to upgrade IMO. Note that Jenkins is simply a find/replace of Hudson to Jenkins and it's a drop in replacement (see http://wiki.jenkins-ci.org/display/JENKINS/Upgrading+from+Hudson+to+Jenkins). WDYT? Thanks -Vincent _______________________________________________ devs mailing list devs(a)xwiki.org http://lists.xwiki.org/mailman/listinfo/devs

Hi devs, As you probably know by now, Hudson has been split in 2: * Jenkins: Kohsuke and all other committers forked and renamed Hudson since there were trademarks issues with Oracle * Hudson: continuing work by Oracle Some more info: http://jenkins-ci.org/content/whos-driving-thing One thing to note is that Sonatype has sided with Oracle: http://www.sonatype.com/people/2011/02/our-focus-on-advancing-hudson-and-ma… Now we need to pick a version: Jenkins or Hudson (community or Oracle). Personally I'm more tempted to follow Jenkins for the time being since: 1) it's the community after all and they're the one who've been doing the work all these past years 2) they're not going to change how jenkins works whereas my understand is that the hudson architecture will be changed (at least that's what Sonatype wants). So in the short period if we want to continue using stable versions the Jenkins path is the safest one. We can then review our choice when Hudson releases new versions. The first official release of Jenkins is out (1.396). See changelog at http://jenkins-ci.org/changelog Since we're using 1.367 it's a good time to upgrade IMO. Note that Jenkins is simply a find/replace of Hudson to Jenkins and it's a drop in replacement (see http://wiki.jenkins-ci.org/display/JENKINS/Upgrading+from+Hudson+to+Jenkins). WDYT? Thanks -Vincent _______________________________________________ devs mailing list devs(a)xwiki.org http://lists.xwiki.org/mailman/listinfo/devs