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.
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.
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.
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.
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.
Since approximately the beginning of the raring development cycle, I had an issue on my thinkpad x220 with google hangouts forcing me to use a tablet or a phone to handle them. What happened is that once I entered a hangout, after 40-60s, my sound was muted and there was no way to get the microphone back on, same for ouptut from other participants. Video was still working pretty well.
The Call for talks for the Crossdesktop devroom at FOSDEM 2013 is getting to its end this very Friday! This year, we'll have some Unity related talks. If you are interested in having one, no time to lose and submit your talk today! Proposals should be sent to the crossdesktop devroom mailing list (you don't have to subscribe).
Last Wednesday, we had our Quickly reboot on air hangout, welcoming the community to ask questions about Quickly and propose enhancement. Here is the recording of the session: As for the previous sessions, we had a lot of valuable feedbacks and participation. Thanks everyone for your help! Your input is tremendous to shape the future of Quickly. We are making a small pause in the Quickly Reboot hangouts, but we will be back soon!
The previous Quickly reboot session about templates was really instructive! It started a lot of really interesting and opened discussions, particularly on the Quickly talks mailing list where the activity is getting higher and higher. Do not hesitate to join the fun here. :) As usual, if you missed the on-air session, it's available here: I've also summarized the session note on the Quickly Reboot wiki page. Next session: Q&A!
Previous sessions The first two hangouts on Quickly reboot about developer feedback were really a blast! I’m really pleased about how much good ideas and questions emerged from those. If you missed them, the hangouts on air are available now on youtube. Go and watch them if you are interested: I’ve also taken some notes during the sessions, here are what I think was important and came from them: hangouts notes.