Re: Jonathan Thomas (JontheEchidna) is a MOTU
在 Wednesday 28 January 2009 14:00:15，Emmet Hikory 写道： congrats > I'm pleased to annouce that Jonathan Thomas has become a MOTU. > Jonathan has been working extensively with the Kubuntu Ninjas, and is > firmly amoung those to thank for both the effective management of > Kubuntu bugs and rapid release of available KDE updates. Please > welcome him to the team. > > -- > Emmet HIKORY signature.asc Description: This is a digitally signed message part. -- Ubuntu-motu mailing list Ubuntu-motu@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu
Jonathan Thomas (JontheEchidna) is a MOTU
I'm pleased to annouce that Jonathan Thomas has become a MOTU. Jonathan has been working extensively with the Kubuntu Ninjas, and is firmly amoung those to thank for both the effective management of Kubuntu bugs and rapid release of available KDE updates. Please welcome him to the team. -- Emmet HIKORY -- Ubuntu-motu mailing list Ubuntu-motu@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu
Re: Early backports to reduce post-release fixes
On Tue, 27 Jan 2009 12:19:07 +0100 Luca Falavigna wrote: >-BEGIN PGP SIGNED MESSAGE- >Hash: SHA1 > >When I was a motu-sru member, I realized the great majority of SRU >candidates to be processed were related to visible bugs (crashes when >doing normal tasks, uninstallable packages, and so on). This kind of >issues could have been addressed in time for the release if widespread >testing was conducted on the affected packages. For basic issues like installability and builability I think we're better of relying on automated tools meant to be used archive wide like puiparts and rebuildd. >We cannot enforce people to upgrade to current development release just >to have more testers, many people believe development release is >completely unusable until release day. I was moderator of Italian >forums, I have several examples of these "isterisms", where people was >scared to see "development branch" in MOTD! These aren't random fears. People without sufficient experience to dig themselves out of a sudden and deep whole should not be running the development release. >How can we help motu-sru to avoid some SRU requests for trivial tasks, >allowing a greater audience to test packages without the need to >upgrade? My proposal is to prepare early backports of the most commonly >used packages in Universe. Starting from Feature Freeze, we could >identify some packages with high popcon and determine if it's worth to >prepare a backport for current stable release (new upstream releases, >new features to be tested, and so on), so the main part of the Ubuntu >users can effectively test packages and report issues, so they can be >fixed in time for the release. > >What do you think? I've certainly done this for packages I'm interested in. It works. Mostly what it needs is interested parties to test backports so we can approve them. Scott K -- Ubuntu-motu mailing list Ubuntu-motu@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu
Re: Early backports to reduce post-release fixes
On Tue, 27 Jan 2009 13:28:20 +0100 Reinhard Tartler wrote: >Luca Falavigna writes: > >> How can we help motu-sru to avoid some SRU requests for trivial tasks, >> allowing a greater audience to test packages without the need to >> upgrade? My proposal is to prepare early backports of the most commonly >> used packages in Universe. Starting from Feature Freeze, we could >> identify some packages with high popcon and determine if it's worth to >> prepare a backport for current stable release (new upstream releases, >> new features to be tested, and so on), so the main part of the Ubuntu >> users can effectively test packages and report issues, so they can be >> fixed in time for the release. > >Short: I like the idea. > >I could imagine a lightweight approach: Activate the ~ubuntu-dev (or >~motu) PPA, and use it as "backports-staging" archive. Proposed policy: > >- proposed package backports should be tracked via a malone bug >- any motu may upload there if he feels that a package should be > backported, mentioning the LP bug number >- the backport teams tracks these bugs and approves backports if > "enough" positive feedback from users has been given in the LP bug > The general standard has been one user reporting it builds, installs, runs. For packages with rdepends, they need to be tested too. This probably seems like a very low standard, but in virtually all cases it proves sufficient. In some cases we ask for more testing if it seems prudent. In short, I don't think we need the PPA step. Scott K -- Ubuntu-motu mailing list Ubuntu-motu@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu
Re: Early backports to reduce post-release fixes
On Tue, 27 Jan 2009 16:25:35 + Iain Lane wrote: ... > Once enabled, they will >receive updates for all packages that a MOTU cares to upload that they >have installed. ... We have a pending spec about improving this situation. Scott K -- Ubuntu-motu mailing list Ubuntu-motu@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu
Re: motu-release organisational meeting
On Tue, 27 Jan 2009 15:05:14 +0100 Stefan Potyra wrote: >Hi, > >On Tuesday 27 January 2009 15:03:11 Luca Falavigna wrote: >> Stefan Potyra ha scritto: >> > What date would suit you? Maybe this Friday, at 14.00h UTC? >> >> Probably I'll be buried in office for that time, I'd rather prefer >> Tuesday, February 3rd at the same timeframe, but I'll try to be there >> anytime (I can't promise I can catch things quickly, though). > >Tuesday, Feb 3 would work for me as well. Others? > Should be fine for me. Scott K -- Ubuntu-motu mailing list Ubuntu-motu@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu
Re: Early backports to reduce post-release fixes
On 27 Jan 2009, at 12:28, Reinhard Tartler wrote: > - the backport teams tracks these bugs and approves backports if > "enough" positive feedback from users has been given in the LP bug I thought the intent wasn't to use this as staging for backports, but to allow users of stable releases to test packages from the current development release without having to upgrade their system wholesale. This will help weed out more bugs in the new version before it becomes harder to fix them post-release. I am a bit concerned that the PPA would suffer from the same problem that -backports and -proposed suffer from now - that there's no easy way for end-users to selectively enable it. Once enabled, they will receive updates for all packages that a MOTU cares to upload that they have installed. Given that this will carry an image of being officially sanctioned in some way, it won't look good if this becomes a sort of "development-release-lite", upgrading end-user applications and potentially destabilising systems. Also, I worry that this will become a short-cut to backporting too. I can see people requesting new upstreams be released to this new PPA, ostensibly "for testing purposes", but really to negate the often- protracted backporting process Just thoughts. The basic premise is good, and I think it would be nice to see some movement in this direction. Iain This message has been checked for viruses but the contents of an attachment may still contain software viruses, which could damage your computer system: you are advised to perform your own checks. Email communications with the University of Nottingham may be monitored as permitted by UK legislation. -- Ubuntu-motu mailing list Ubuntu-motu@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu
Re: motu-release organisational meeting
Hi, On Tuesday 27 January 2009 15:03:11 Luca Falavigna wrote: > Stefan Potyra ha scritto: > > What date would suit you? Maybe this Friday, at 14.00h UTC? > > Probably I'll be buried in office for that time, I'd rather prefer > Tuesday, February 3rd at the same timeframe, but I'll try to be there > anytime (I can't promise I can catch things quickly, though). Tuesday, Feb 3 would work for me as well. Others? Cheers, Stefan. signature.asc Description: This is a digitally signed message part. -- Ubuntu-motu mailing list Ubuntu-motu@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu
Re: motu-release organisational meeting
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Stefan Potyra ha scritto: > What date would suit you? Maybe this Friday, at 14.00h UTC? Probably I'll be buried in office for that time, I'd rather prefer Tuesday, February 3rd at the same timeframe, but I'll try to be there anytime (I can't promise I can catch things quickly, though). - -- . ''`. Luca Falavigna : :' : Ubuntu MOTU Developer `. `'` Debian Maintainer `- GPG Key: 0x86BC2A50 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.8 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkl/FB8ACgkQnXjXEYa8KlAGKwCfZbpxjByCts2a17MgBdYmmT9/ FTUAn2Y98a06HOJoacZu/GObephLJkJL =GoZ4 -END PGP SIGNATURE- -- Ubuntu-motu mailing list Ubuntu-motu@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu
Re: Early backports to reduce post-release fixes
Luca Falavigna writes: > How can we help motu-sru to avoid some SRU requests for trivial tasks, > allowing a greater audience to test packages without the need to > upgrade? My proposal is to prepare early backports of the most commonly > used packages in Universe. Starting from Feature Freeze, we could > identify some packages with high popcon and determine if it's worth to > prepare a backport for current stable release (new upstream releases, > new features to be tested, and so on), so the main part of the Ubuntu > users can effectively test packages and report issues, so they can be > fixed in time for the release. Short: I like the idea. I could imagine a lightweight approach: Activate the ~ubuntu-dev (or ~motu) PPA, and use it as "backports-staging" archive. Proposed policy: - proposed package backports should be tracked via a malone bug - any motu may upload there if he feels that a package should be backported, mentioning the LP bug number - the backport teams tracks these bugs and approves backports if "enough" positive feedback from users has been given in the LP bug -- Gruesse/greetings, Reinhard Tartler, KeyID 945348A4 -- Ubuntu-motu mailing list Ubuntu-motu@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu
motu-release organisational meeting
Hi motu-release members, with FeatureFreeze approaching at Feb 19, I guess it'd be good if we schedule an organisational meeting. What do you think? What date would suit you? Maybe this Friday, at 14.00h UTC? Cheers, Stefan. signature.asc Description: This is a digitally signed message part. -- Ubuntu-motu mailing list Ubuntu-motu@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu
Re: Help and sponsor request for package in sponsor queue
On Tue, 2009-01-27 at 11:59 +0100, Cesare Falco wrote: > Hi all, > > I apologize, I've messed up status/assignment etc. on my update > request for sdlmame in the sponsor queue. :( > > Could you please confirm bug report settings are right now? > https://bugs.launchpad.net/bugs/318304 That looks fine to me. Someone should attend to it soon. Thanks, James -- Ubuntu-motu mailing list Ubuntu-motu@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu
Early backports to reduce post-release fixes
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 When I was a motu-sru member, I realized the great majority of SRU candidates to be processed were related to visible bugs (crashes when doing normal tasks, uninstallable packages, and so on). This kind of issues could have been addressed in time for the release if widespread testing was conducted on the affected packages. We cannot enforce people to upgrade to current development release just to have more testers, many people believe development release is completely unusable until release day. I was moderator of Italian forums, I have several examples of these "isterisms", where people was scared to see "development branch" in MOTD! How can we help motu-sru to avoid some SRU requests for trivial tasks, allowing a greater audience to test packages without the need to upgrade? My proposal is to prepare early backports of the most commonly used packages in Universe. Starting from Feature Freeze, we could identify some packages with high popcon and determine if it's worth to prepare a backport for current stable release (new upstream releases, new features to be tested, and so on), so the main part of the Ubuntu users can effectively test packages and report issues, so they can be fixed in time for the release. What do you think? - -- . ''`. Luca Falavigna : :' : Ubuntu MOTU Developer `. `'` Debian Maintainer `- GPG Key: 0x86BC2A50 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.8 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkl+7asACgkQnXjXEYa8KlCy7QCeKKfPkgIeZWJFaCKFGypqL/8Q oDUAoJe53+L8qyfSlkanp9ZIb9ea1Agq =JT8A -END PGP SIGNATURE- -- Ubuntu-motu mailing list Ubuntu-motu@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu
Help and sponsor request for package in sponsor queue
Hi all, I apologize, I've messed up status/assignment etc. on my update request for sdlmame in the sponsor queue. :( Could you please confirm bug report settings are right now? https://bugs.launchpad.net/bugs/318304 they should be, providing these are the most recent updating progress specs: https://wiki.ubuntu.com/MOTU/Sponsorship/SponsorsQueue Thanks! Cesare "wallyweek" Falco. -- Ubuntu-motu mailing list Ubuntu-motu@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu
