Ubuntu

Release early, release often, release every 4h!

It's been a long time I didn't talk about our daily release process on this blog. For those who are you not aware about it, this is what enables us to release continuously most of the components we, as the ubuntu community, are upstream for, to get into the baseline. Historic Some quick stats since the system is in place (nearly since last December for full production): we are releasing as of now 245 components to distro every day (it means, everytime a meaningfull change is in any of those 245 components, we will try to release it).

Versioning schema change in daily release

Just a quick note on Daily Releases (process to upload to the ubuntu distribution more than 200 components Canonical is upstream for in various ubuntu series). After some discussions on #ubuntu-release today, we decided to evoluate the daily release versioning schema: we previously had <upstream_version>daily<yy.mm.dd>-0ubuntu1 as a daily release schema in the regular case multiple releases a day for the same component would give: <upstream_version>daily<yy.mm.dd>.minor-0ubuntu1, where minor is an incremental digit for maintenance branch, we previously had <upstream_version>daily<yy.

Followup UDS session on application lifecycle

I hope that everyone enjoyed the new virtual UDS format as we did. :) However, don't despair, it's not really *over* yet! The discussion around the application lifecycle[1] was covering a too large spectrum and we didn't get time to properly finish discussing it. As we didn't want to run over other sessions, we decided to reschedule it just after UDS. The new follow-up session "Application model: lifecycle" will happen this Friday, March 8, 16:00 – 16:25 UTC.

Unity: release early, release often… release daily! (part 5 and conclusion)

This post is part of the Unity daily release process blog post suite. After a week to let people ask questions about the daily release process, I guess it's time to catch up and conclude this serie with a FAQ and some thoughts for the future. FAQ The FAQ is divided in multiple sequences depending on your role in the development of ubuntu, with the hope that you will be able to find what you are looking for quicker this way.

Unity: release early, release often… release daily! (part 4)

This post is part of the Unity daily release process blog post suite. You hopefully recovered from your migraine on reading yesterday's blog post on the insight of daily release and are hungry for more. What's? That's not it? Well, mostly, but we purposely dismissed one of the biggest point and consequences on having stacks: they depends on each other! Illustrating the problem Let's say that Mr T. has an awesome patch for the indicator stack, but this one needs as well some changes in Unity and is not retro-compatible.

Unity: release early, release often… release daily! (part 3)

This post is part of the Unity daily release process blog post suite. Now that we know how branches are flying to trunk and how we ensure that the packaging metadata are in sync with our delivery, let's swing to the heart of the daily release process! Preliminary notes on daily release This workflow is heavily using other components that we rely on. In addition to our own tool for daily release, which is available here, we needed to use jenkins for scheduling, controlling and monitoring the different parts of the process.

Unity: release early, release often… release daily! (part 2)

This post is part of the Unity daily release process blog post suite. As part of the new Unity release procedure, let's first have look at the start of the story of a branch, how does it reach trunk? The merge procedure Starting the 12.04 development cycle, we needed upstream to be able to reliably and easily get their changes into trunk. To ensure that every commits in trunk pass some basic unit tests and doesn't break the build, that would obviously mean some automation would take place.

Unity: release early, release often… release daily! (part 1)

This post is part of the Unity daily release process blog post suite. This is part one, you can find: part 2 on upstream merge process part 3 on the daily release machinery part 4 on how dependencies are handled between stacks part 5 for a FAQ and conclusion For almost the past 2 weeks (and some months for other part of the stacks), we have automated daily release of most of the Unity components directly delivered to Ubuntu raring.