With the JUC Paris 2012 call for papers open, it's important to mention that we are also looking for sponsors for the various Jenkins User Conferences that are being planned around the world right now!

Currently there are four conferences being put together right now:

• JUC Paris
• JUC New York
• JUC San Francisco
• JUC Antwerp

If your company is heavily invested in Jenkins or interested in reaching the kind of audience that will be at a JUC (highly technical, motivated) then you should consider becoming a sponsor one of these conferences (link below)!

Sponsor the Jenkins User Conference

(Editor's note: Apologies for the delay in getting this wrap-up out, it's been quite a busy month!)

This year has already been full of milestones, the first of which being our first birthday as an open source project. The second major milestone for the project was that we went to FOSDEM 2012, arguably the largest volunteer-organized and operated open source conference on the planet.

We had a couple of things going on at FOSDEM that merit a mention:

• The Jenkins project had a stand in the K building, the same building where the Free Java, Config and Systems Management, and a few other pertinent dev rooms were located
• The Jenkins project gave away 2 free copies of John Smart's book: "Jenkins: The Definitive Guide" (thanks to O'Reilly!)
• Community member R. Tyler Croy gave a talk on running the Jenkins project infrastructure with Puppet
• The O'Reilly folks brought 10+ Jenkins books to sell at their stand.
• Project founder Kohsuke Kawaguchi and a number of project members held a constructive UI Enhancements discussion.

We were very fortunate to have so many Jenkins contributors in attendance, who all helped with the Jenkins stand, introducing people to Jenkins and much more.

FOSDEM in their own words

(English text follows the French text)

Après le succès de la Jenkins User Conference l’an dernier à San Francisco et à l’intérêt qu’elle a soulevé, nous organisons cette année la JUC dans quatre grande villes à travers le monde. La premiére étape de cette tournée est la JUC 2012 à Paris, le 17 avril. La conférence aura lieu la veille de Devoxx France dans les mêmes locaux. La date a été spécialement choisie pour que vous puissiez faire d’une pierre deux coups, ou plutôt deux confs !

On February 2nd, 2011 the first release of Jenkins, version 1.396, was made available for public consumption. Thus marking a new beginning for many of us who had come to rely on this very versatile piece of software and wanted to see it continue to thrive.

Along with some other bug fixes, the 1.396 release of Jenkins included a very important changelog item:

Fixed a trademark bug that caused a considerable fiasco by renaming to Jenkins

On behalf of the core Jenkins team and the governance board I would like to extend a extremely large Thank You! to all of the plugin developers, bug filers, wiki page editors, book authors and the users who have helped grow Jenkins into the project it is today.

Some of the tidbits from our highlight reel:

• As of this writing there have been 54 releases of Jenkins
• Jenkins now supports writing plugins in Ruby as well as Java (more languages in the process)
• We have 7 high-speed mirrors streaming Jenkins packages to users around the world.
• There are now over 450 different plugins available for Jenkins
• Over 80 donors participated in our end of year fundraising drive
• 5 "Long Term Support" releases have been published by the Jenkins community, offering users a slower moving upgrade target (supported even further by CloudBees' Enterprise Jenkins product)
• Public project governance meetings are held and recorded (almost) every couple of weeks.
• More than 340 individuals contribute on GitHub to the project in some form or another.
• About 750 members of the developers mailing list and around 1700 on the users mailing list

There are many other impressive sounding numbers I could rattle off, but the list is far too long to be interesting.

The project isn't perfect and nor is the software, but we're off to a fine start and I hope you'll join us in making this next year of Jenkins even better than the first.