Hi,
Those of you who read opensuse-factory mailing list too, will already be aware, but for those who aren't, I would like to make it more official:
We won't be able to release 12.2 in time. We didn't catch up with the slip of the milestones and beta, so I can't release RC1 now - and delaying RC1 means delay of 12.2 too.
As I don't want to move 12.2 release into august due to vacation time, my thinking about rescheduling is this:
- next week I will release what I have as 12.2-Beta2 - after that we will split away openSUSE:12.2 from factory to put it under deep freeze for pure bug fixes. - Mid of July we can have RC1 - August will see more updates, but no real action - Release mid of September
Greetings, Stephan
Hi,
If we delay it, which I think is a normal action having in mind its state at the moment, can we at least allow kde 4.9 and texlive 2012 in?
Alin
On Thursday 14 of June 2012 09:47EN, Alin M Elena wrote:
If we delay it, which I think is a normal action having in mind its state at the moment, can we at least allow kde 4.9 and texlive 2012 in?
As I understand it, the reason for the delay is to get enough time to cleanup the mess 12.2/Factory is currently in (which is incompatible with "RC" status). I don't think putting new (beta) version of KDE in is going to help (or at least not going to do any harm).
Michal Kubeček
As I understand it, the reason for the delay is to get enough time to cleanup the mess 12.2/Factory is currently in (which is incompatible with "RC" status). I don't think putting new (beta) version of KDE in is going to help (or at least not going to do any harm).
I doubt the mess is caused by kde... and kde release is announced for 1st of August... if 12.2 is released in mid September would be silly to do it without it. 4.9 trunk is building already on obs and runs without major issues... I am sure the kde team would be able to get all the things together, as usually, on time.
texive is a beast to build but I think Werner and Stephan would put it in shape soon.
regards, Alin
On Thursday, June 14, 2012 10:19:40 Alin M Elena wrote:
As I understand it, the reason for the delay is to get enough time to cleanup the mess 12.2/Factory is currently in (which is incompatible with "RC" status). I don't think putting new (beta) version of KDE in is going to help (or at least not going to do any harm).
I doubt the mess is caused by kde... and kde release is announced for 1st of August... if 12.2 is released in mid September would be silly to do it without it. 4.9 trunk is building already on obs and runs without major issues... I am sure the kde team would be able to get all the things together, as usually, on time.
texive is a beast to build but I think Werner and Stephan would put it in shape soon.
Those are both large stacks and integration of them takes time and might cause other fallout. Let's fix what we have first before opening additional construction sites,
Andreas
On 06/14/2012 11:38 AM, Andreas Jaeger wrote:
On Thursday, June 14, 2012 10:19:40 Alin M Elena wrote:
As I understand it, the reason for the delay is to get enough time to cleanup the mess 12.2/Factory is currently in (which is incompatible with "RC" status). I don't think putting new (beta) version of KDE in is going to help (or at least not going to do any harm).
I doubt the mess is caused by kde... and kde release is announced for 1st of August... if 12.2 is released in mid September would be silly to do it without it. 4.9 trunk is building already on obs and runs without major issues... I am sure the kde team would be able to get all the things together, as usually, on time.
texive is a beast to build but I think Werner and Stephan would put it in shape soon.
Those are both large stacks and integration of them takes time and might cause other fallout. Let's fix what we have first before opening additional construction sites,
That's right. When I read about the delay, I immediately thought, that at least I can push the yet to be released syslog-ng 3.4 in with some wonderful new features. But then realized, that a rock solid 3.3 has a lot more benefits. And syslog-ng is a leaf package, no other packages depend on it... Lets leave it for OBS! Bye, CzP
On 14.06.2012 10:47, Alin M Elena wrote:
Hi,
If we delay it, which I think is a normal action having in mind its state at the moment, can we at least allow kde 4.9 and texlive 2012 in?
No. And I don't even want to discuss it.
Greetings, Stephan
On Thu, Jun 14, 2012 at 11:46 AM, Stephan Kulow coolo@suse.de wrote:
On 14.06.2012 10:47, Alin M Elena wrote:
Hi,
If we delay it, which I think is a normal action having in mind its state at the moment, can we at least allow kde 4.9 and texlive 2012 in?
No. And I don't even want to discuss it.
For those of use wanting KDE4.9 post install, we should be able to install it just as we do now with KDE4.8.4... from the OBS repos.
C.
On Thursday 14 Jun 2012 10:43:37 Stephan Kulow wrote:
- next week I will release what I have as 12.2-Beta2
What's the curent freeze status in this case?
There's a couple of major bug fixes in core Go language package that were addressed in todays 1.0.2 release which I had planned to address with an update/maintenence incident after 12.2 under the assumption that we were frozen for now according to your schedule timeline: http://www.suse.de/~coolo/opensuse_12.2/
On 14.06.2012 11:03, Graham Anderson wrote:
On Thursday 14 Jun 2012 10:43:37 Stephan Kulow wrote:
- next week I will release what I have as 12.2-Beta2
What's the curent freeze status in this case?
There's a couple of major bug fixes in core Go language package that were addressed in todays 1.0.2 release which I had planned to address with an update/maintenence incident after 12.2 under the assumption that we were frozen for now according to your schedule timeline: http://www.suse.de/~coolo/opensuse_12.2/
The more frozen we are, the better your arguments for the updates have to be (and the version number should not be part of your arguments).
Your arguments: + major bug fixes + easily tested stack as it only affects a group of packages + all updates from one devel project
My questions will come down to: - why not do a maintenance update later? - how many people will be affected by a broken go release in 12.2 to warrent my time evaluating your arguments :)
Greetings, Stephan
On Thursday 14 Jun 2012 12:02:25 Stephan Kulow wrote:
My questions will come down to:
- why not do a maintenance update later?
- how many people will be affected by a broken go release in 12.2 to warrent my time evaluating your arguments
I think given these questions I'll plan for a maintenance update later on. I have to prepare one for 12.1 anyway and since go hackers have been working around the issues already I'd rather not tie up other peoples time at this point in the schedule.
Cheers the noo, Graham
-
Alin M Elena -
Andreas Jaeger -
C -
Graham Anderson -
Michal Kubeček -
Peter Czanik -
Stephan Kulow