Hi Jean, For other project i am working on, if a bug exists in a branch and in trunk we are used to open two bugs. That allow us to be able to do pretty deep modification in trunk to fix the bug and implement a "simpler fix" in branch since the code in branch is not supposed to deeply change. So regarding my experience in other projects: - a bug marked oscar-5.0 should be fixed and lead to oscar-5.0.1 - a bug marked trunk should be fixed and lead to any version > 5.0
After that i am not the involved at any time in the definition of the rules for the OSCAR bug management. :-) My 2 cents, On Friday 06 April 2007 09:33, Jean Parpaillon wrote: > Hi all, > I'm writing diving into branches, bugs and milestones to propose a roadmap. > I have a questions/suggestions: bugs tagged with version "branch-5-0" > should not exist anymore. May you have a look at bugs with this version to: > - either tag them with version "5.0" > - either close them. > so that we could after set the right milestone. I have not seen any rules > about OSCAR versions, but I imagine that if we have critical bugs on 5.0, > we should release a 5.0.1. > > Does the following rule seems correct ?: > - if there are critical bugs on 5.0, we release a 5.0.1 > - if bugs still exist on 5.0 but are enhancement/tasks, let's tag them with > milestone "5.1". > > Regards, > Jean -- Geoff ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Oscar-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/oscar-devel
