Re: QA releases RFC

anatoly techtonik wrote: > Hello Arnaud, > Great scheme, esp. picture, but some clearifications required: > 1. Where issues are reported? Maintainers already receive > notifications on new bugs in their packages. But note about QA > pulled release and link with details is welcomed. > 2. If maintainer opted-out - do not contact him, since he already > received a note and aware of issue. Better provide a way to him > to respond his status/willingness/time to resolve in a note above. > 3. "Put a notice..." - in a special QA DIV. > 4. Notice on a page only if a bug is definitely serious and it is > impossible to pull older release, because of other bugs. > 5. Not just "Fix and roll", but send maintainer patch and > testcase for review. Provide a ways to avoid similar bugs in the > future. This case arises only if the maintainer does not react in a timely fashion so sendind a patch makes little sense. > 7. Mention CVS modifications in QA branch. BTW, CVS modifications > on software packages can be filtered and remailed to all their > maintainers. > > * blocks can be numbered =) Where ? > >>Those fields would be QA-core restricted access for privacy concerns. > > Not necessary. > >>* status field, maintainers can indicate if they are on vacation, >>unvailable, unable/uninterested to work on their packages anymore. > > Useless, because you can simply forgot to check/uncheck these > and if people would like to abandon their packages - they can easily > say so or let bug list grow. Better provide a way to vote or rate > items (like on PHP.NET) > > >>* IM field, maintainers can give their IM contact information for fast >>turnaround. > > If it will be field with "QA only" checkbox why not. That's the idea. > You better define how to opt-out package - should the package be out-opted > or maintainer himself? Per package. > If opt-out option on a package is changed - a notice should be sent to > all it's maintainers. > > There this issues and reports will be stored? We will have an internal tool to start with. I have updated the html[1] page and the pdf[2]. Arnaud. [1]: HTML http://www.limbourg.com/qa_releases/ [2]: PDF http://www.limbourg.com/qa_releases/qa_releases.pdf