Mailinglist Archive: zypp-devel (116 mails)
| < Previous | Next > |
Re: [yast-devel] Re: [zypp-devel] ZYPP: TRUNK->BETA REFACTORING-BACKUP-10_3->STABLE
- From: Michael Andres <ma@xxxxxxx>
- Date: Wed, 20 Jun 2007 13:56:38 +0200
- Message-id: <20070620115638.GA32031@xxxxxxx>
On Wed, Jun 20, Jiri Srain wrote:
> Dne st??eda 20 ??erven 2007 13:31 Michael Andres napsal(a):
> > svn copy -r 5789
> > http://svn.opensuse.org/svn/zypp/trunk/
> > http://svn.opensuse.org/svn/zypp/branches/REFACTORING-BACKUP-10_3
> >
> >
> > REFACTORING-BACKUP-10_3 is a snapshot of the latest libzypp revision
> > we comitted to STABLE.
> >
> > TRUNK is now submitted to BETA only, until all the outdated Source*
> > stuff is removed, an all applications switched to the new Repo*
> > classes.
> >
> >
> > How to handle it in YaST?
>
> In the past, we created a temporayr branch for the new stuff and kept
> submitting trunk to STABLE (so that it was consistent in the whole
> repository).
>
> Any reason why not to do it this way?
So I'll create REFACTORING-10_3 branches for yast and zypp,
and we leave trunk as it is.
Sorry for the noise.
--
cu,
Michael Andres
+------------------------------------------------------------------+
Key fingerprint = 2DFA 5D73 18B1 E7EF A862 27AC 3FB8 9E3A 27C6 B0E4
+------------------------------------------------------------------+
Michael Andres YaST Development ma@xxxxxxxxxx
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: zypp-devel+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: zypp-devel+help@xxxxxxxxxxxx
> Dne st??eda 20 ??erven 2007 13:31 Michael Andres napsal(a):
> > svn copy -r 5789
> > http://svn.opensuse.org/svn/zypp/trunk/
> > http://svn.opensuse.org/svn/zypp/branches/REFACTORING-BACKUP-10_3
> >
> >
> > REFACTORING-BACKUP-10_3 is a snapshot of the latest libzypp revision
> > we comitted to STABLE.
> >
> > TRUNK is now submitted to BETA only, until all the outdated Source*
> > stuff is removed, an all applications switched to the new Repo*
> > classes.
> >
> >
> > How to handle it in YaST?
>
> In the past, we created a temporayr branch for the new stuff and kept
> submitting trunk to STABLE (so that it was consistent in the whole
> repository).
>
> Any reason why not to do it this way?
So I'll create REFACTORING-10_3 branches for yast and zypp,
and we leave trunk as it is.
Sorry for the noise.
--
cu,
Michael Andres
+------------------------------------------------------------------+
Key fingerprint = 2DFA 5D73 18B1 E7EF A862 27AC 3FB8 9E3A 27C6 B0E4
+------------------------------------------------------------------+
Michael Andres YaST Development ma@xxxxxxxxxx
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: zypp-devel+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: zypp-devel+help@xxxxxxxxxxxx
| < Previous | Next > |