Dne 23.9.2013 15:34, Josef Reidinger napsal(a): [...]
Well, I propose different approach to do it only when needed, as there is a lot of modules which doesn't have maintainer and that is not touched at all, so it doesn't need maintenance branch. Maybe it will nicely show usage of modules.
It might sound good, but the problem is if you touch such an "unmaintained" module after like 6 months you will very likely (I'd say almost for sure, see later) forget to create the maintenance branch. And then after another 6 months it is pretty hard to find the correct commit backwards for creating a maintenance branch for a bugfix. Yes, you can checkout the OBS sources and find the last commit, but it's not trivial (checking just the *.changes file may not be enough as there might be just a small fix not mentioned in *.changes...). Therefore I suggest creating the branch for all relevant (included in openSUSE) repositories globally. And here starts the interesting part, I just have checked which repositories do NOT have 12.2 and 12.3 branches and surprisingly the number is quite high (see the attached files for complete list): - 84 repositories do not have 12.2 branch - 74 repositories do not have 12.3 branch (I have manually filtered out some obsoleted packages or product specific (SLE) packages, but I could overlook something in the quick search so these are probably not perfectly exact numbers, but they still demonstrate the problem quite nicely.) What's worse, even a base package like yast2-core does NOT have the maintenance branches so it's quite difficult to find the difference between releases or since the last release (e.g. "git log origin/openSUSE-12_2..origin/openSUSE-12_3" does not work). And that's really stupid. We could avoid this by adding the branches globally. -- Ladislav Slezák Appliance department / YaST Developer Lihovarská 1060/12 190 00 Prague 9 / Czech Republic tel: +420 284 028 960 lslezak@suse.com SUSE