[yast-devel] Branching openSUSE 10.3 -- Proposal
Hi, Despite the fact that most of us are still fixing openSUSE 10.3 bugs, there are some commits that should go to the "after 10.3 only". Our proposal is to branch openSUSE 10.3 on Monday 24th after 18:00 (with RC2 if possible)- Mvidner is a volunteer for doing that :) Please, speak up if you don't like to proposal. Thanks & Bye Lukas -- Lukas Ocilka, YaST Developer (xn--luk-gla45d) ----------------------------------------------------------------- SUSE LINUX, s. r. o., Lihovarska 1060/12, Praha 9, Czech Republic
On Thu, Sep 20, 2007 at 03:23:12PM +0200, Lukas Ocilka wrote:
Hi,
Despite the fact that most of us are still fixing openSUSE 10.3 bugs, there are some commits that should go to the "after 10.3 only".
Our proposal is to branch openSUSE 10.3 on Monday 24th after 18:00 (with RC2 if possible)- Mvidner is a volunteer for doing that :)
I have just created the 10.3 maintenance branches: For YaST, at r41075 http://svn.opensuse.org/svn/yast/branches/SuSE-Linux-10_3-Branch For Zypp, at r7353 http://svn.opensuse.org/svn/zypp/branches/SuSE-Linux-10_3-Branch So for 10.3 fixes, use the branch (and merge the changes to the trunk right away). I will update the branch descriptions in the wiki shortly. http://en.opensuse.org/YaST/Development/SVN_branches http://en.opensuse.org/Libzypp/Development_Branches -- 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
On Tue, Sep 25, Martin Vidner wrote:
I have just created the 10.3 maintenance branches:
For YaST, at r41075 http://svn.opensuse.org/svn/yast/branches/SuSE-Linux-10_3-Branch For Zypp, at r7353 http://svn.opensuse.org/svn/zypp/branches/SuSE-Linux-10_3-Branch
Increased libzypp major version on TRUNK to 4. SuSE-Linux-10_3-Branch stays with 3. -- cu, Michael Andres +------------------------------------------------------------------+ Key fingerprint = 2DFA 5D73 18B1 E7EF A862 27AC 3FB8 9E3A 27C6 B0E4 +------------------------------------------------------------------+ Michael Andres YaST Development ma@novell.com SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) Maxfeldstrasse 5, D-90409 Nuernberg, Germany, ++49 (0)911 - 740 53-0 +------------------------------------------------------------------+ -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
On Tuesday 25 September 2007 12:02:27 Michael Andres wrote:
On Tue, Sep 25, Martin Vidner wrote:
I have just created the 10.3 maintenance branches:
For YaST, at r41075 http://svn.opensuse.org/svn/yast/branches/SuSE-Linux-10_3-Branch For Zypp, at r7353 http://svn.opensuse.org/svn/zypp/branches/SuSE-Linux-10_3-Branch
Increased libzypp major version on TRUNK to 4.
We should implement the shared library policy on trunk. that means libzypp should be libzypp4 to allow paralell installations of it. http://en.opensuse.org/Packaging/Shared_Library_Packaging_Policy Duncan -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
On Tue, Sep 25, Duncan Mac-Vicar Prett wrote:
On Tuesday 25 September 2007 12:02:27 Michael Andres wrote:
On Tue, Sep 25, Martin Vidner wrote:
I have just created the 10.3 maintenance branches:
For YaST, at r41075 http://svn.opensuse.org/svn/yast/branches/SuSE-Linux-10_3-Branch For Zypp, at r7353 http://svn.opensuse.org/svn/zypp/branches/SuSE-Linux-10_3-Branch
Increased libzypp major version on TRUNK to 4.
We should implement the shared library policy on trunk. that means libzypp should be libzypp4 to allow paralell installations of it.
Do we want to allow parallel installations?
http://en.opensuse.org/Packaging/Shared_Library_Packaging_Policy
According to this policy we had a frequently changing packagename: libzypp400 libzypp403 libzypp408 ... (soname changes whenever LIBZYPP_COMPATMINOR changes) Apart from that, it does not make much sense to have different versions in parallel, if they do not use at least the same database schema. And even with the same schema we may run into trouble, because different versions may store different attribute sets in the DB. If we want to do it anyway: What about translations and parser schema (.rng .rnc)? We have to include the soname in path or filename: /usr/share/locale/...../zypp400.mo /usr/share/zypp400/schema/xmlstore /yum What about config files and binaries? Shall we move them to an other package (zypper? or a new one). /etc/zypp/zypp.conf /usr/bin/package-manager /usr/bin/package-manager-su /usr/lib/zypp/zypp-migrate-sources /usr/lib/zypp/zypp-query-pool -- cu, Michael Andres +------------------------------------------------------------------+ Key fingerprint = 2DFA 5D73 18B1 E7EF A862 27AC 3FB8 9E3A 27C6 B0E4 +------------------------------------------------------------------+ Michael Andres YaST Development ma@novell.com SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) Maxfeldstrasse 5, D-90409 Nuernberg, Germany, ++49 (0)911 - 740 53-0 +------------------------------------------------------------------+ -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
Ahoj!
I have just created the 10.3 maintenance branches:
I know, this is implicitly clear, but I'd like to make it explicit in case some people (esp. new yastees) don't know: Effective new 10.3 maitenance branch creation * Please start incrementing versions of your packages from 2.16.0 in the trunk. * Keep 2.15 versioning series for 10.3 fixes Thanks B. -- \\\\\ Katarina Machalkova \\\\\\\__o YaST developer __\\\\\\\'/_ & hedgehog painter
participants (5)
-
Duncan Mac-Vicar Prett -
Katarina Machalkova -
Lukas Ocilka -
Martin Vidner -
Michael Andres