True words Colin. I'll repeat this one more time - let's reset this discussion and FOCUS on reliable and possible to implement in 4 months features.
I'd suggest that all features which will not be on wiki page will be treated as a act of ignorance and arrogance. So if someone will push newer wersion of python and this will be not on the wiki then we should follow idea based on Prague meeting and revert this python change. Wysłano z BlackBerry® w Orange -----Original Message----- From: Colin Close <[email protected]> Date: Tue, 03 Dec 2013 10:46:15 To: <[email protected]>; Cooker OpenMandriva<[email protected]> Subject: Re: [OM Cooker] DRAFT - Release plan for 2014.0 On Tuesday 03 Dec 2013 09:29:49 Tomasz Paweł Gajc wrote: > Let's focus on features that we want to present to the world. Currently wiki > page for 2014.0 specifications is almost not touched. I thought we are done > with model like "Hey just update some packages, do the freeze and branch and > then we will figure out what new features brings this release". > > > P.S. > > Paulo i doubt releasing 2013.1 in 2014 year will do an good. > > Wysłano z BlackBerry® w Orange > > -----Original Message----- > From: [email protected] > Date: Mon, 2 Dec 2013 16:11:18 > To: Cooker OpenMandriva<[email protected]> > Cc: Tomasz Pawe? Gajc<[email protected]> > Subject: Re: [OM Cooker] DRAFT - Release plan for 2014.0 > > Robert Xu escreveu: > > ... > > > > Well, then Cooker better unbreak itself. That's troublesome because we've > > already upgraded the toolchain and etc. > > On Dec 2, 2013 6:15 AM, "Tomasz Pawe? Gajc" <[email protected]> wrote: > > We could have a 2013.1. But I think it is better to avoid too many > forks, and keep only a single cooker fork a few months before release. > I believe a 2013.1 would need a very good reason to, e.g. some large > lts contract. > > What is really important is ensuring proper upgrades from official > releases. I only managed to get a working cooker again by installing > 2013.0 and upgrading from there to cooker. My previous cooker installs > I had been updating for >4 months broke real bad (all of them > started from an openmandriva iso rc). > > >> No, it will use cooker. > >> Wys?ano z BlackBerry® w Orange > >> > >> -----Original Message----- > >> From: Robert Xu <[email protected]> > >> Sender: [email protected]: Sun, 1 Dec 2013 > >> 18:55:34 > >> To: Cooker OpenMandriva<[email protected]> > >> Reply-To: Cooker OpenMandriva <[email protected]> > >> Subject: Re: [OM Cooker] DRAFT - Release plan for 2014.0 > >> > >> On 1 December 2013 09:46, Tomasz Pawe? Gajc <[email protected]> wrote: > >> > Hello, > >> > > >> > as i mentioned on last TC meeting, i'm providing a draft release plan for > >> > 2014.0 OMV distribution release. > >> > > >> > Everything what you need is here on a dedicated wiki page for 2014.0 > >> > https://wiki.openmandriva.org/en/2014.0 > >> > also a pdf version is attached to this e-mail. > >> > > >> > Simple steps: > >> > * Feature planing stage - we gather all needed features which we would > >> like to > >> > have - 2013-12-15 > >> > > >> > I've prepared page for this, so please fill it with your ideas, but > >> first make > >> > them reasonable and "fittbale" for 2014 release cycle. > >> > https://wiki.openmandriva.org/en/2014.0/Specifications > >> > > >> > * Mass rebuild - 2014-01-20 - rebuilding and fixing all failed packages > >> > > >> > * Alpha - 2014-01-31 - releasing ISO with press anouncement > >> > > >> > * Mass rebuild - 2014-02-15 - rebuilding and fixing all failed packages > >> > > >> > * Beta - 2014-02-28 - releasing ISO with press anouncement > >> > > >> > * Version freeze - 2014-03-11 - uploading new verson of packages to > >> cokker > >> > main repository is forbidden unless Q&A will allow > >> > > >> > * RC1 - 2014-03-21 - releasing ISO with press anouncement > >> > > >> > * RC2 - 2014-04-04 - releasing ISO with press anouncement > >> > > >> > * GA - 2014-04-18 - releasing ISO with press anouncement > >> > > >> > * Maybe some release party ? :) > >> > > >> > I hope we made a clear decision in Prague and last TC meeting that we > >> want > >> > this release to be done smooth and quickly, so this means we should not > >> plan > >> > any major brakages, only keep updated kernel, gcc, xorg, perl, KDE, > >> artwork, > >> > ples few more based on accepted features. > >> > I think we should consider to release a working ARM port with 2014. > >> > > >> > RFC are welcome, also please fill the features. > >> > > >> > P.S. > >> > > >> > Sorry for not being on IRC and stuff but i got flu and feel not very > >> well. > >> > > >> > > >> > >> Ok, I just need one point of clarification here: > >> > >> - Is 2014.0 using the 2013.0 repositories? > >> > >> -- > >> Robert Xu :: protocol.by/rxu > >> > >> > >> > > > > > > > Hi, Tomasz you are absolutely right, it's crazy people are saying one thing and doing another and this is exactly the fragmentation that I talked about in Prague, We have already screwed up as we now in a position where if we wish to implement an interim release based on the same tool chain we will have to use 2013 as a base. The intermediate release was to be latest KDE, a lightweight window manager (properly finished), the latest kernel plus all the bugfixes and updates that are applied in the interim. In addition I would suggest the following a proper fix for the installer such that uefi based machines will boot in uefi mode. There is still a great deal of work to do to get the even the basic release fully compliant there are still references to Mandriva in the code and information pages the basic documentation is yet to be updated and translated. There are packages in contrib that do not have the correct keys and probably countless others that require attention which we can only address as people file bugs against them. Much more than this and I believe we are going beyond what we discussed so please let's get a sense of perspective here, It took a year to get a basic (in some areas unfinished) release out I cannot envisage and interim release containing much more that that which I have detailed in six months. We must also consider our development resources as there is interim work that needs to be done on the OpenMandriva tools used to create the distribution these will need to be used to produce the point release. We cannot struggle along any longer with the current iso production tools they are inadequate for the way we work; the filesystems used are not suitable for use with a livecd type distro as there is too little filesystem space and many of our difficulties with 2013.0 arose from this limitation. It is currently a painful business to produce test isos we can only do it efficiently on ABF but that efficiency is immediately degraded by having to download the iso (this is slow for some). Some additional work is likely to be needed on the installer not only to address the uefi issues but also graphics booting. There are operational deficiency's in ABF regarding updates and QA that must be addressed. All these things take time and given our resources to expect anything much more than that detailed here is just unrealistic. I hope the next minor release will leave us in a position where all the ground work is completed and we can start building a full release with all the bells and whistles. Best, Colin Colin Close QA Team
