We've been very busy over the last couple of months with lots of changes that most people will never notice.
Branches pushed to Launchpad are now immediately available over http to anonymous readers of the branch, which includes the loggerhead code browser.
Code review email changes
When proposing a branch for review the initial emails and subsequent comments will now come in order. Previously if someone commented before the script that generated the diff was run, the comment would be emailed out first, now it isn't.
Teams requested to review now get email
Everyone in the team that is requested to review will get email now. This is a blessing for those that want it, and almost a curse for those that aren't interested. Launchpad adds a number of email headers to help users with filtering of email. Here is an example from an email I received:
X-Launchpad-Message-Rationale: Reviewer @drizzle-developers
Since it was a team that was requested to review, there is the @drizzle-developers
added to the X-Launchpad-Message-Rationale. If I was personally asked to review, the header would just say Reviewer
Build branch to archive
This was the original name of the feature, but it is more about recipes now. A recipe is a collection of instructions on how to build a source package. We are still testing this internally, but I'm hoping to get this enabled on edge very soon. This will be extended to add daily builds.
What does this really mean?
Lets say you want to have a daily build of a project, like gwibber
. You would then create a recipe that uses trunk as a base branch, merge in the packaging info, and say "Please build this every day into my PPA"
. And Launchpad will.