News from the Launchpad team
We’re releasing Launchpad 1.2.4 in the early hours of 1st May 2008. To roll out the new code, we need to take Launchpad offline.
Going offline: 00.00 UTC 1st May 2008.
Coming back: 02.00 UTC 1st May 2008.
We’re sorry if you want to use Launchpad at that time.
If you’re involved in a project that uses Launchpad’s bug tracker, you’ll know that one of the most important roles is the bug contact.
Next week, when we release Launchpad 1.2.4, we’re changing the name of project and distribution bug contact to bug supervisor. The role stays the same but we think the new name better reflects what it has become.
This does not apply to package bug contacts who will be renamed to bug subscriber, as their role is quite different to bug supervisor for distros and projects
Originally, the main part of being a bug contact was dealing with bug notifications. Whoever was in the bug contact role - whether a team or individual - would receive email about new bugs and changes to existing bugs for their project, package or distribution.
Since our February release, bug mail is open to everyone. If you want to get email notifications about a particular project, package or distro’s bug activity, all you have to do is subscribe. Similarly, bug contacts can unsubscribe from those bug notifications.
So, the name “bug contact” no longer seems appropriate.
Bug contacts - or bug supervisors after April 30th - are automatically subscribed to the relevant bug notifications. In addition, they can:
The change is already in place on our Edge environment. Take a look at Launchpad’s bugs overview page on Edge to see it in place.
Hi,
Since the last Launchpad release you may have noticed a few emails and blog
posts referring to unexpected issues with Launchpad. I thought you might
like to know more about what was causing them, and how we are addressing them.
Launchpad’s operational environment is hosted on several machines in order to
provide adequate response times given our user load. Previously, we had to
maintain separate, and complex, configuration settings for each of the servers.
This was not very conducive to developing and deploying new features, nor
supporting the existing infrastructure. The situation was becoming
unmaintainable, and we had made careful plans to resolve these problems.
To address this limitation, we migrated the existing configuration settings
over to a standard, site-wide, hierarchical system. We’re confident that this
new configuration system will also provide us with a much more robust, stable
and maintainable operational environment. However, the rollout of this new
system has resulted in an undesirable level of shake-out due to the
complexities of the Launchpad services involved and the complexities of the
old configuration system.
On behalf of the entire Launchpad Development Team, I’d like to offer our
sincerest apologies for any inconvenience this may have caused you. We ask you
for your continued understanding as we seek to improve the Launchpad service.
Joey Stanford
Launchpad Releases Team Manager
Hi Gang,
Just a quick heads up that we uncovered a problem today with Launchpad Mailing List notifications. You may have received a mailing list notification from Launchpad with a funny URL that looks like
https://xmlrpc.lp.internal/~rinchen/+editemails
These courtesy emails are normally sent out (with correct URLs) when a team you are a member of creates a new Launchpad Mailing List. The email is still valid despite the incorrect URL.
You should visit your Launchpad person page and view your email settings. At the bottom you will see “Mailing list subscriptions”. From here you can manage your Launchpad mailing list subscriptions.
Here’s a short cut to that page: https://launchpad.net/people/+me/+editemails
Sorry for the inconvenience. We should have this fixed by tomorrow.
Joey Stanford
You are currently browsing the Launchpad blog weblog archives for the month April, 2008.
Longer entries are truncated. Click the headline of an entry to read it in its entirety.
© 2007 Canonical Limited.