Hi,
I played with dates and holidays and it's *very*, *very* tight ;(
What I came up with is basically:
20121003: Milestone 0 20121108: Milestone 1 20121213: Milestone 2 It's 5 weeks between 1 and 2, but releasing one in between is not worth it and I can make 1 earlier and 2 later ;( 20130117: Beta1 20130207: RC1 20130228: RC2 20130307: GM 20130313: FCS
In theory this can work out, but in practice we again have gained 94 packages not building ;(
Greetings, Stephan
Quoting Stephan Kulow coolo@suse.de:
Hi,
I played with dates and holidays and it's *very*, *very* tight ;(
What I came up with is basically:
20121003: Milestone 0 20121108: Milestone 1 20121213: Milestone 2 It's 5 weeks between 1 and 2, but releasing one in between is not worth it and I can make 1 earlier and 2 later ;( 20130117: Beta1 20130207: RC1 20130228: RC2 20130307: GM 20130313: FCS
In theory this can work out, but in practice we again have gained 94 packages not building ;(
I think the schedule CAN work, BUT it is mandatory that we the 'large' stacks start committing to what they are planning to submit for 12.3 soon and work on that until around BETA1 (latest RC1) at which time we really should have only minor updates and fixes coming down the way.
Beta1 to GM is roughly 2 month... which is basically what we used in 12.2 to 'stabilize' the system (the famous slip period).
From a GNOME perspective I can say that, given this schedule, we will be on GNOME 3.6.<latest patch level>.
Best regards, Dominique
15 октября 2012 12:35:23 Stephan Kulow написал(а):
Hi,
I played with dates and holidays and it's *very*, *very* tight ;(
What I came up with is basically:
20121003: Milestone 0 20121108: Milestone 1 20121213: Milestone 2 It's 5 weeks between 1 and 2, but releasing one in between is not worth it and I can make 1 earlier and 2 later ;( 20130117: Beta1 20130207: RC1 20130228: RC2 20130307: GM 20130313: FCS
In theory this can work out, but in practice we again have gained 94 packages not building ;(
Greetings, Stephan
Adding new packages to factory is possible up to Beta1 or Milestone 2? I'm going to add most part of packages from science repository to factory.
On 15.10.2012 13:01, Dmitry Roshchin wrote:
Adding new packages to factory is possible up to Beta1 or Milestone 2? I'm going to add most part of packages from science repository to factory.
For Beta1 it should be fine.
Greetings, Stephan
On Mon, Oct 15, 2012 at 6:35 AM, Stephan Kulow coolo@suse.de wrote:
Hi,
I played with dates and holidays and it's *very*, *very* tight ;(
What I came up with is basically:
20121003: Milestone 0 20121108: Milestone 1 20121213: Milestone 2 It's 5 weeks between 1 and 2, but releasing one in between is not worth it and I can make 1 earlier and 2 later ;( 20130117: Beta1 20130207: RC1 20130228: RC2 20130307: GM 20130313: FCS
In theory this can work out, but in practice we again have gained 94 packages not building ;(
Greetings, Stephan
Very, very tight with a community project like this makes me nervous. sysvinit removal is still part of that as far as I know.
I'd still vote for a respin to be released sometime in the winter (jan-mar) with the latest kde/gnome and then release 12.3 in July. (A 4 month delay).
Greg
On Mon, 2012-10-15 at 08:49 -0400, Greg Freemyer wrote:
Very, very tight with a community project like this makes me nervous. sysvinit removal is still part of that as far as I know.
I'd still vote for a respin to be released sometime in the winter (jan-mar) with the latest kde/gnome and then release 12.3 in July. (A 4 month delay).
Greg
What does this mean exactly? We already have a respin with GNOME 3.6 available now. (And I presume similarly for KDE 4.92?)
Bryen
On Mon, Oct 15, 2012 at 8:54 AM, Bryen M Yunashko suserocks@bryen.com wrote:
On Mon, 2012-10-15 at 08:49 -0400, Greg Freemyer wrote:
Very, very tight with a community project like this makes me nervous. sysvinit removal is still part of that as far as I know.
I'd still vote for a respin to be released sometime in the winter (jan-mar) with the latest kde/gnome and then release 12.3 in July. (A 4 month delay).
Greg
What does this mean exactly? We already have a respin with GNOME 3.6 available now. (And I presume similarly for KDE 4.92?)
I saw Dominique's reply which may shoot this down, but for completeness:
I was thinking of a re-spin that was more formally announced and that was available at: http://software.opensuse.org/
Maybe it would have a formal "12.2-respin" and "12.2-respin updates" repos. Even bugzilla could be updated to allow reporting.
Give it a short support cycle of say 6 months so that people could move to 12.3 once it was released.
Greg
On Mon, 2012-10-15 at 09:07 -0400, Greg Freemyer wrote:
I saw Dominique's reply which may shoot this down, but for completeness:
I was thinking of a re-spin that was more formally announced and that was available at: http://software.opensuse.org/
Maybe it would have a formal "12.2-respin" and "12.2-respin updates" repos. Even bugzilla could be updated to allow reporting.
That's more of a marketing thing than a development thing. Perhaps we don't do enough to promote the many respins and customized openSUSE's that exist out there in Studio and elsewhere.
Give it a short support cycle of say 6 months so that people could move to 12.3 once it was released.
That just adds more work to those who are responsible for maintaining and updating supported releases. And this causes further confusion to users who download official releases. Furthermore, it creates a misleading impression because now people who see "12.2 Respin" available in our official repositories will assume that the original 12.2 is bad and had to be re-done.
Let's stick to the original intent of this thread which is whether Coolo's schedule proposal is viable for those who have the time and ability to work on the next release.
Bryen
Greg
Quoting Greg Freemyer greg.freemyer@gmail.com:
On Mon, Oct 15, 2012 at 6:35 AM, Stephan Kulow coolo@suse.de wrote:
I'd still vote for a respin to be released sometime in the winter (jan-mar) with the latest kde/gnome and then release 12.3 in July. (A 4 month delay).
That makes only very partially sense, as: - I'd have to split my attention given to Factory at this moment to integrate GNOME 3.6 into 12.2 respins (which is mostly done anyway... but so far we can say 'best effort' and not 'fully supported' - It leaves the question about maintenance of the respins vs the original 12.2 completely open. - Respins usually target one desktop. Updating one desktop can badly break any other DE in the system. Would we need to address this? If yes: you deviate even more focus away from Factory.
The respins are best left 'out of the official' channels and are, as already done, to be provided best-effort. This clearly gives the right expectations for users installing them: Installing the KDE 49 respin I won't be too surprised if any of the other desktops break on the way.. there is no integration work done)
Best regards, Dom
On 10/15/2012 06:35 AM, Stephan Kulow wrote:
Hi,
I played with dates and holidays and it's *very*, *very* tight ;(
What I came up with is basically:
20121003: Milestone 0 20121108: Milestone 1 20121213: Milestone 2 It's 5 weeks between 1 and 2, but releasing one in between is not worth it and I can make 1 earlier and 2 later ;( 20130117: Beta1 20130207: RC1 20130228: RC2 20130307: GM 20130313: FCS
In theory this can work out, but in practice we again have gained 94 packages not building ;(
Well, lets see if we cannot address this problem I have some ideas, see you in Prague ;)
Robert
On Monday 2012-10-15 12:35, Stephan Kulow wrote:
I played with dates and holidays and it's *very*, *very* tight ;(
What I came up with is basically: [...] 20130207: RC1 20130228: RC2 20130307: GM 20130313: FCS
What is FCS?
On 12.11.2012 13:38, Jan Engelhardt wrote:
On Monday 2012-10-15 12:35, Stephan Kulow wrote:
I played with dates and holidays and it's *very*, *very* tight ;(
What I came up with is basically: [...] 20130207: RC1 20130228: RC2 20130307: GM 20130313: FCS
What is FCS?
Hi Jan,
From http://en.wikipedia.org/wiki/FCS: First customer shipment, a development stage of hardware and software
It's sometimes also referred as GA, but due to the easy confusion with GM I like to avoid that term.
Greetings, Stephan
On Monday, November 12, 2012 13:38:38 Jan Engelhardt wrote:
On Monday 2012-10-15 12:35, Stephan Kulow wrote:
I played with dates and holidays and it's *very*, *very* tight ;(
What I came up with is basically: [...]
20130207: RC1 20130228: RC2 20130307: GM 20130313: FCS
What is FCS?
"First customer shipment" - release to the public. We need roughly a week to get the infrastructure and mirrors ready,
Andreas
Mandag den 12. november 2012 13:42:24 skrev Andreas Jaeger:
On Monday, November 12, 2012 13:38:38 Jan Engelhardt wrote:
On Monday 2012-10-15 12:35, Stephan Kulow wrote:
I played with dates and holidays and it's *very*, *very* tight ;(
What I came up with is basically: [...]
20130207: RC1 20130228: RC2 20130307: GM 20130313: FCS
What is FCS?
"First customer shipment" - release to the public.
Maybe we should change it to "First Community Shipment" ;-)
-
Andreas Jaeger -
Bryen M Yunashko -
Dmitry Roshchin -
Dominique Leuenberger a.k.a DimStar -
Greg Freemyer -
Jan Engelhardt -
Martin Schlander -
Robert Schweikert -
Stephan Kulow