Mailinglist Archive: opensuse-gnome (44 mails)
| < Previous | Next > |
Re: [opensuse-gnome] 2.19 Plan
- From: JP Rosevear <jpr@xxxxxxxxxx>
- Date: Mon, 23 Apr 2007 14:35:20 -0400
- Message-id: <1177353320.3374.269.camel@xxxxxxxxxxxxxxxxxxxxx>
On Mon, 2007-04-23 at 18:57 +0200, Stanislav Brabec wrote:
> Michael Wolf wrote:
> > On Mon, 2007-04-23 at 09:43 -0400, JP Rosevear wrote:
> > > We need a plan to cover GNOME 2.19 now that its being released.
> > > Normally I would say move 2.18.1 to G:S and keep updating it there, but
> > > in this case we have the /opt/gnome -> /usr move to deal with, we'd
> > > break anyone on 10.2 and older for sure. Any thoughts on what to do?
> >
> > I think we should rename GNOME:STABLE to GNOME:GNOME-2.16 and
> > GNOME:UNSTABLE to GNOME:GNOME-2.18. We should also create
> > GNOME:GNOME-2.20 for the 2.19 and eventual 2.20 work. GNOME:Community
> > should probably remain as-is.
>
> I would like it, too. But it was rejected in past after a long
> discussion, so there is only chance to move it out of the BS as an
> static and no longer updated stuff.
I definitely pushed back on this, I didn't want to end up with 4 or 5
"supported" build services. However things have changed somewhat - the
length of time until 10.3 means two shipping versions of GNOME probably
and the /opt/gnome -> /usr move wasn't factored in. I guess what we
should do is rename G:U to G:216opt or something, move 2.18 to G:S
(built only for 10.2 and factory) and start in on 2.19 in G:U.
The downside of course is not being able to get more testing on 10.2 -
unless we can get that compatibility package built asap which might make
2.18 feasible on 10.2.
-JP
--
JP Rosevear <jpr@xxxxxxxxxx>
Novell, Inc.
--
To unsubscribe, e-mail: opensuse-gnome+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-gnome+help@xxxxxxxxxxxx
> Michael Wolf wrote:
> > On Mon, 2007-04-23 at 09:43 -0400, JP Rosevear wrote:
> > > We need a plan to cover GNOME 2.19 now that its being released.
> > > Normally I would say move 2.18.1 to G:S and keep updating it there, but
> > > in this case we have the /opt/gnome -> /usr move to deal with, we'd
> > > break anyone on 10.2 and older for sure. Any thoughts on what to do?
> >
> > I think we should rename GNOME:STABLE to GNOME:GNOME-2.16 and
> > GNOME:UNSTABLE to GNOME:GNOME-2.18. We should also create
> > GNOME:GNOME-2.20 for the 2.19 and eventual 2.20 work. GNOME:Community
> > should probably remain as-is.
>
> I would like it, too. But it was rejected in past after a long
> discussion, so there is only chance to move it out of the BS as an
> static and no longer updated stuff.
I definitely pushed back on this, I didn't want to end up with 4 or 5
"supported" build services. However things have changed somewhat - the
length of time until 10.3 means two shipping versions of GNOME probably
and the /opt/gnome -> /usr move wasn't factored in. I guess what we
should do is rename G:U to G:216opt or something, move 2.18 to G:S
(built only for 10.2 and factory) and start in on 2.19 in G:U.
The downside of course is not being able to get more testing on 10.2 -
unless we can get that compatibility package built asap which might make
2.18 feasible on 10.2.
-JP
--
JP Rosevear <jpr@xxxxxxxxxx>
Novell, Inc.
--
To unsubscribe, e-mail: opensuse-gnome+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-gnome+help@xxxxxxxxxxxx
| < Previous | Next > |