-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hi,
As we are already working on SLE 11 SP2 features, I've checked the branches in use and found out that only limited number of modules is in SP2 branch [1], compare that to SP1 [2].
What is the current approach? Is everyone who intends to work on a feature for SP2 expected to branch their module in time when they start working?
Thanks in advance for clarification Lukas
#1 http://svn.opensuse.org/svn/yast/branches/SuSE-Code-11-SP2-Branch/ #2 http://svn.opensuse.org/svn/yast/branches/SuSE-Code-11-SP1-Branch/
- --
Lukas Ocilka, Appliances Department, Novell Inc.
Dne St 13. dubna 2011 11:23:33 Lukas Ocilka napsal(a):
Hi,
As we are already working on SLE 11 SP2 features, I've checked the branches in use and found out that only limited number of modules is in SP2 branch [1], compare that to SP1 [2].
What is the current approach? Is everyone who intends to work on a feature for SP2 expected to branch their module in time when they start working?
I think so. So far it is working.
Dne 13.4.2011 11:23, Lukas Ocilka napsal(a):
Hi,
As we are already working on SLE 11 SP2 features, I've checked the branches in use and found out that only limited number of modules is in SP2 branch [1], compare that to SP1 [2].
IIRC the reason is to have only the changed modules in SP2 branch and copy the package from SP1 branch only when needed. Basically to avoid loosing fixes from SP1 and to avoid double commit when doing an update for SP1.
--
Best Regards
Ladislav Slezák Yast Developer ------------------------------------------------------------------------ SUSE LINUX, s.r.o. e-mail: lslezak@suse.cz Lihovarská 1060/12 tel: +420 284 028 960 190 00 Prague 9 fax: +420 284 028 951 Czech Republic http://www.suse.cz/
Hi,
Am Mittwoch, 13. April 2011, 15:33:12 schrieb Ladislav Slezak:
Dne 13.4.2011 11:23, Lukas Ocilka napsal(a):
Hi,
As we are already working on SLE 11 SP2 features, I've checked the branches in use and found out that only limited number of modules is in SP2 branch [1], compare that to SP1 [2].
IIRC the reason is to have only the changed modules in SP2 branch and copy the package from SP1 branch only when needed. Basically to avoid loosing fixes from SP1 and to avoid double commit when doing an update for SP1.
Important: take care of the new maintenance concept! The plan was, that most features and fixes should still be fixed and maintained in SP1-Updates (also for SP2). But it seems, that the Rules are not really clear. There are still discussions around how to handle this in practice.
I would suggest to wait with doing any work for SP2 until PM, TPM, etc. knows what they want and how this should be done.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Dne 14.4.2011 10:18, Michael Calmer napsal(a):
I would suggest to wait with doing any work for SP2 until PM, TPM, etc. knows what they want and how this should be done.
I'm afraid that we already have plenty of features to be implemented and not enough time anyway. IMO we should be working on SP2 already unless these is something even more important than that.
Bye Lukas
-
Jiri Suchomel -
Ladislav Slezak -
Lukas Ocilka -
Michael Calmer