Hey Erich,
Here are the svn rules for the project in my own lingo. I'm cc'ing the core
list as a reminder to everyone. This is not a smackdown, because I for
sure do not want to stop any development or bug fixing.
1. On a frozen branch, you can only check in code to fix priority 9 bugs.
Additionally, since a 9 is a 'showstopper', it should not be closed out
until tested/verified by a third party. In practice, if there's something
you've been working on for the release and want to get in really badly,
sometimes a new bug can be generated and upped. I think the system should
support development and not squish it.
2. Only the release manager, currently me, or a designated alternate can
up a bug to priority nine. If you just ask me directly, often i'll just
say go do it (like with the patched c3 rpm's). Otherwise, it may take me a
day or so to read the sf bug traffic and do something about it.
3. Our traditional rule is check in nothing that breaks the trunk. Of
everything, this is probably the worst, because it can shut down all
development. We have a database development branch now, and could add
another if the need is there.
So lets OSCAR on in a friendly fashion, but please stay inside the rules.
-- John
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
Oscar-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/oscar-devel
