Mailinglist Archive: opensuse-gnome (216 mails)
| < Previous | Next > |
Re: [opensuse-gnome] GNOME:STABLE and GNOME:UNSTABLE
- From: Michael Wolf <maw@xxxxxxxxxx>
- Date: Wed, 03 Oct 2007 19:23:50 -0500
- Message-id: <1191457430.4288.44.camel@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
On Wed, 2007-03-10 at 12:30 -0400, Joe Shaw wrote:
> Hi,
>
> On 10/3/07, Michael Wolf <maw@xxxxxxxxxx> wrote:
> > * GNOME:UNSTABLE
> >
> > We'll also repopulate GNOME:UNSTABLE with the contents of the
> > revelant packages as they currently exist in Factory. However, the
> > future of this repository will be different. When GNOME 21 comes
> > out, we'll be tracking it closely.
> >
> > At the same time, we'll stop directly updating the GNOME packages
> > directly in Factory. Instead, packages from GNOME:UNSTABLE will be
> > (automatically, I hope) synced to Factory on a regular basis.
> >
> > Tarballs for GNOME 21.1 are due on 20071029, so we'll start updating
> > it then, but we can start improving our .specs as discussed in
> > http://en.opensuse.org/GNOME/Patches sooner than that.
>
> How will this setup work when it comes time to release a new version
> of openSUSE? In particular, what version (and from repo) will we
> ultimately ship GNOME from? How does the alignment of GNOME releases
> and openSUSE releases affect this? Etc.
Good questions.
GNOME 2.22.0 is about 6 months away, and openSUSE 11.0 is about 8 months
away. So, assuming we will ship 2.22.0 in 11.0, then when 2.22.0 ships,
we can create a new repository [0], populated from the contents of
GNOME:UNSTABLE at the time. If we had real revision control, we'd call
this a branch. After "branching", GNOME 2.23 can go into
GNOME:UNSTABLE.
Upon creation of that new repository, a switch will be flicked, and
Factory will pull its updates from there.
Upon release of 11.0, another set of switches will be flicked: Factory
will once again pull from GNOME:UNSTABLE, and 11.0 internally will pull
from that new repository.
Does that make sense? Is it even what you were asking about? (jpr on
irc thought you were asking about something else, but I'll answer the
question as I understood it. :))
This is complicated, but I haven't worked out a better way to invite
people who don't work for Novell to get more involved than they already
are. I think it would be greatly simplified if we used bzr, hg, or git
[1] throughout.
[0] What to call it? GNOME:Factory? GNOME:2.22.x? GNOME:11.0? I
think the latter, GNOME:11.0, makes the most sense, since fixes for our
stuff, post 11.0 release, should continue going through the Build
Service.
[1] I guess this makes the order of my preferences obvious, but I'd be a
lot happier with any of them than I am now.
--
To unsubscribe, e-mail: opensuse-gnome+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-gnome+help@xxxxxxxxxxxx
> Hi,
>
> On 10/3/07, Michael Wolf <maw@xxxxxxxxxx> wrote:
> > * GNOME:UNSTABLE
> >
> > We'll also repopulate GNOME:UNSTABLE with the contents of the
> > revelant packages as they currently exist in Factory. However, the
> > future of this repository will be different. When GNOME 21 comes
> > out, we'll be tracking it closely.
> >
> > At the same time, we'll stop directly updating the GNOME packages
> > directly in Factory. Instead, packages from GNOME:UNSTABLE will be
> > (automatically, I hope) synced to Factory on a regular basis.
> >
> > Tarballs for GNOME 21.1 are due on 20071029, so we'll start updating
> > it then, but we can start improving our .specs as discussed in
> > http://en.opensuse.org/GNOME/Patches sooner than that.
>
> How will this setup work when it comes time to release a new version
> of openSUSE? In particular, what version (and from repo) will we
> ultimately ship GNOME from? How does the alignment of GNOME releases
> and openSUSE releases affect this? Etc.
Good questions.
GNOME 2.22.0 is about 6 months away, and openSUSE 11.0 is about 8 months
away. So, assuming we will ship 2.22.0 in 11.0, then when 2.22.0 ships,
we can create a new repository [0], populated from the contents of
GNOME:UNSTABLE at the time. If we had real revision control, we'd call
this a branch. After "branching", GNOME 2.23 can go into
GNOME:UNSTABLE.
Upon creation of that new repository, a switch will be flicked, and
Factory will pull its updates from there.
Upon release of 11.0, another set of switches will be flicked: Factory
will once again pull from GNOME:UNSTABLE, and 11.0 internally will pull
from that new repository.
Does that make sense? Is it even what you were asking about? (jpr on
irc thought you were asking about something else, but I'll answer the
question as I understood it. :))
This is complicated, but I haven't worked out a better way to invite
people who don't work for Novell to get more involved than they already
are. I think it would be greatly simplified if we used bzr, hg, or git
[1] throughout.
[0] What to call it? GNOME:Factory? GNOME:2.22.x? GNOME:11.0? I
think the latter, GNOME:11.0, makes the most sense, since fixes for our
stuff, post 11.0 release, should continue going through the Build
Service.
[1] I guess this makes the order of my preferences obvious, but I'd be a
lot happier with any of them than I am now.
--
To unsubscribe, e-mail: opensuse-gnome+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-gnome+help@xxxxxxxxxxxx
| < Previous | Next > |