Differences between revisions 9 and 12 (spanning 3 versions)
Revision 9 as of 2005-01-08 03:17:42
Size: 705
Editor: anonymous
Comment:
Revision 12 as of 2009-03-16 03:35:57
Size: 859
Editor: anonymous
Comment: converted to 1.6 markup
Deletions are marked like this. Additions are marked like this.
Line 2: Line 2:
Since the RC bugs are a critical issue, every developer should make sure his/her packages are as neat as possible. perhaps we are too lame and don't give our packages the love they deserve? if so, what can we do about it? more co-maintenance? more checks? harder policy? Since the RC bugs are a critical issue, every developer should make sure his/her packages are as neat as possible.  Perhaps we are too lame and don't give our packages the love they deserve? If so, what can we do about it? More co-maintenance? More checks? Harsher policy?
Line 12: Line 12:
Perhaps there's something missing in the New Maintainer's vetting/training process?
"Due diligence" comes to mind.

--
Line 15: Line 19:
 * [[Slum]]

Since the RC bugs are a critical issue, every developer should make sure his/her packages are as neat as possible. Perhaps we are too lame and don't give our packages the love they deserve? If so, what can we do about it? More co-maintenance? More checks? Harsher policy?

Note: I am probably the lamest of all and this isn't meant to insult anyone

Watch files could be used more often to simplify the tracking and packaging of latest versions of upstream programs.

-- true, but that's not an issue for release-quality (at least not very much) -- robert

-- Perhaps there's something missing in the New Maintainer's vetting/training process? "Due diligence" comes to mind.

-- See also:

Back to ReleaseProposals