In May, we launched Jenkins Office Hours. This was inspired by Jenkins Ruby hack sessions by cowboyd, and the idea is to use an interactive online meeting to drive some sub-projects, bootstrap new plugin developers by pointing them to the right extension points, and/or bringing existing community members to discuss some specific key parts of Jenkins and its plugins.
The first two meetings were very popular, but our trial WebEx account expired, and since then we were looking for a sponsor to host this event. And I am happy to report that with a help from Max Spring, now we can get the office hours going again.
So the Jenkins office hours will be bi-weekly events, starting this Wednesday (6/29). See the wiki page for details and agenda. Looking forward to seeing you!
We have released 1.409.1, our first long-term support (LTS) release, from the Jenkins project.
The idea of the LTS release is to provide a second release line the favors more stability and bug fix only maintenance. This release line branches off from a bit old Jenkins release (in this case 1.409), and we will only put important backported bug fixes. We'll keep releasing 1.409.2, 1.409.3, and so on, as such bugs appear, and in several months (our current thinking is 3 months) we'll designate another release and repeat this process all over again. I think it provides more comfortable upgrade path for larger deployments. For more about this, see Wiki.
In large companies that use Jenkins in a large scale, there often is a team of people who looks at incoming Jenkins release, tests it with their environments and their plugins, and then let their internal group consume them. With this release line, I'm calling for them to join the effort on this branch. Vojtech Juranek from Red Hat is already helping us tremendously, so is Yahoo in choosing the base release line and backporting. But it'd be great to get more people on board, as I think it'll benefit everyone to have a larger number of eyeballs on the same code.