On Wed, Mar 17, 2010 at 10:14:01AM +0100, Marc 'HE' Brockschmidt wrote: > I would be happy if you could point out any specific insanity in the > notes of the IRC meeting from yesterday. If it seems fine, it would be > great if you could work on drafting a release update informing the > project about the current status of squeeze and the plans for the > immediate future. FWIW, I have at the moment no idea what the status of > our release goals is, that's a subject someone needs to research.
This seems worthwhile. Would you like me to do this? > Some of the transitions waiting to happen could profit from someone > checking if everything alright. This means finding out which packages > are affected, which of these need sourceful uploads and coordination > with the maintainers of these packages. You know the business. If it > should go to testing, care needs to be taken to not entangle it with any > of the other ongoing transitions. When all of that is checked and > prepared, the transitioning package can be uploaded and binNMUs be > scheduled. If you want to do this yourself, it shouldn't be a problem to > give you direct access to w-b. I consider this one to be iffy ethically. > We also need to get the number of rc bugs down if we want to release > squeeze this year. To this end, it would be great if one or more > (virtual) BSPs could be organized, possibly focussed at a specific type > of bug. > Besides the number of RC bugs, we also have some widely used packages > where maintainers are overwhelmed by the number of bugs filed against > their packages (KDE, Gnome, iceweasel, ...) While not strictly a release > issue, triaging (and possibly fixing) bugs can be integrated into a BSP > to give people something easier (but nonetheless tedious :-/) to do. I think I am underqualified for this one because I have never understood the point of a virtual BSP. I'll be happy to expend a minimal amount of effort trying to expend a minimal amount of effort on inspiring others to set up more in-person BSPs (with a triage focus). > There is also the issue of the release notes. This was a problem for > lenny, and it doesn't look like it will get any better for > squeeze. The release notes need to be updated for squeeze and upgrade > and installation tests on different configurations should be > organized. It's a bit early to do it, as many components of squeeze are > not done yet, but at least finding people who would be interested in > working on this would be great. I also think I am underqualified for this one since I've never read any release notes. > I guess that's all I have on my current release todo list. Does anything > of that sound like you could live with yourself if you would do it? Answered briefly above. -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100318023831.ga2...@scru.org