Hi hackers, BEGIN RULES - trunk will be for 11.2, and I create http://svn.opensuse.org/svn/yast/branches/SuSE-Code-11-Branch/ (in 1 hour, at 14:00 CET, so that this does not catch you completely surprised) - Code-11 will be a "side-trunk", the place of (cautious) development for SLE11 and its service packs. That is, in sequence, the following branches will be created from Code-11, to maintain updates that are diverging or backported from Code-11: SuSE-Linux-11_1-Branch SuSE-SLE-11-Branch SuSE-SLE-11-SP1-Branch SuSE-SLE-11-SP2-Branch Code-11 versions will have 3 components, 2.17.*, and all the other branches will bear 2.17.*.* It differs from the Code 10 concept in simplifying the decision where to commit: * Committing to a branch means a maintenance update. * Committing to Code-11 (side-trunk) means development/fixes scheduled for later. END RULES Compare to Code 10 ( http://en.opensuse.org/index.php?title=YaST/Development/SVN_branches&oldid=67380 ) where *-SPx-Branch is once a place of development and then becomes maintenance. Duncan objected that this scheme creates too many branches and that we are too flexible in favor of Novell product needs, whereas we should send YaST on a more independent way: http://lizards.opensuse.org/2008/11/07/yast-releases-independent-of-opensuse... I think he is right but we should do it for 11.2 and beyond, not for SLE 11. -- Martin Vidner, YaST developer http://en.opensuse.org/User:Mvidner Kuracke oddeleni v restauraci je jako fekalni oddeleni v bazenu -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org