Posts

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.

Time for a Quickly reboot?

Quickly is the recommended tool for opportunistic developers on ubuntu. When we created it 3 years ago, we made some opinionated choices, which is the essence of the project. We had back then a lot of good press coverage and feedbacks (Linux Weekly News, arstechnica, Zdnet, Maximum PC review, Shot of jak and some more I can’t find on top of my head…) Some choices were good, some were wrong and we adapted to the emerging needs that happened along the road.

Quickly: a path forward?

Seeing the amount of interests we saw around Quickly the past last years was really awesome! Now that we have some more detailed view on how people are using the tool, it’s time to collect and think about those data to see how we can improve Quickly. With all the new tools available like hangouts on air, it can be also now time to experiment how we can use them and use this opportunity to have a very open collaboration process as well as trying to attract more people to contribute to it.