On Thu, Jun 17, 2010 at 01:03:36PM +0200, Marc Espie wrote: > On Thu, Jun 17, 2010 at 11:02:20AM +0100, Federico G. Schwindt wrote: > > On Thu, Jun 17, 2010 at 07:49:15AM +0200, Steven Mestdagh wrote: > > > Federico G. Schwindt [2010-06-16, 17:00:19]: > > > > hi, > > > > > > > > is there any reason to keep 2.5 around and specially as the default? > > > > 2.6 has been stable for some time now and all the ports should work > > > > with > > > > it. itoh, 2.5 is not maintained anymore except for some sporadic > > > > security > > > > updates. > > > > having to check your ports against 2.5 and 2.6 is time consuming (I'm > > > > not > > > > considering 2.4 as should only used for zope), but unfortunately is > > > > required > > > > for a number of reasons. > > > > so i propose to remove 2.5 and apply the diff below. this also > > > > removes > > > > mentions to 2.3 and updates the comments to mention other ports > > > > hardcoding > > > > the python version. > > > > comments? objections? oks? > > > > > > Ok to move to 2.6 as default, but I think it's better to leave 2.5 in tree > > > for a while. It does not hurt and can still be removed later. > > > > even if we move the default to 2.6 we will still require to test against > > 2.5. > > that's one of my reason to remove it and not simply change the default. > > what's your reason to leave it? > > I think we can live 2.5 in. Having it in doesn't mean everything must be > tested against it. If it breaks, it breaks. And then you'll know if it impacts > real people.
ok, if that's the case I have no problems leaving 2.5 around and moving to 2.6 as default. f.-
