Author
As part of determining What’s Next?, Jonathan (our Product Strategist) and I will be attending UDS Oneiric next week (May 9th - May 13th) in Budapest. If you are running a session where you need input from Launchpad, or working on a Ubuntu project that would require …
In my last post, I explained how squads doing maintenance picked the next bug to work on. But how does it work for the other squads? We have two squad that works on a project which is usually a feature. In this context, a feature means something that will take a team of 4-5 …
To many people, Launchpad development looks like a black box. People asks for thing in various places (the bug tracker, the mailing lists, IRC, directly to developers, or simply wish it out loud) and then, often unexpectedly, Lauchpad will change. We strive to work in the open, …
Launchpad’s web interface will be read-only, with other aspects offline, for around 90 minutes from 08.00 UTC on the 4th May 2011. Starts: 08.00 UTC 4th May 2011 Expected to end by: 09.30 UTC 4th May 2011 This is to allow for a structural update to Launchpad’s …
We are now two months away from our next Thunderdome. How are we doing in regards with the objectives set for that milestone? You may recall from my last post the objectives: have no timeouts with a cut-off at 9s; have an empty critical bugs queue; getting a slot free on our …
Launchpad has been operating in the squad structure for two months now. From my point of view, things have been going very well. We are making steady progress on fixing timeouts, OOPSes, regressions and other operational issues. The blue squad switched to maintenance after …
In twelve hours from this posting, Launchpad’s web interface will be read-only, with other aspects offline, for around 90 minutes. This is to allow us to make an update to the structure of the Launchpad database. This replaces the previous read-only period announced for Feb …
Read more of Launchpad read-only 09.00 UTC 11th February 2011 →
Following the SourceForge compromise, the SSL certificate for SourceForge subversion changed. A bug on their end prevents us from automatically importing from their SVN repositories. Until that bug is resolved, all SourceForge code imports are disabled. 2011/02/14 update: We …
We’ve made some changes to how we organise the Launchpad team! We’re no longer divided into application-based teams (Bugs, Code, Foundations, Registry, Soyuz and Translations). Instead, we now have five cross-domain engineering squads: three focused on features and …
From today, all Launchpad bugs, code, questions and blueprints are tracked under the one launchpad project. We’ve already moved everything from the individual projects over to the parent launchpad project. All you need do differently is search/file bugs, questions and …
Read more of Changing how we track Launchpad's bugs, questions and blueprints →