Date: Sat, 1 Dec 2007 14:25:08 +0100 From: Erik Trulsson <ertr1013@student.uu.se> To: David Southwell <david@vizion2000.net> Cc: freebsd-ports@freebsd.org Subject: Re: duration of the ports freeze Message-ID: <20071201132508.GA33039@owl.midgard.homeip.net> In-Reply-To: <200712010514.55274.david@vizion2000.net> References: <33640.194.74.82.3.1196149681.squirrel@galain.elvandar.org> <4750F55B.9030604@highperformance.net> <200712010308.43873.david@vizion2000.net> <200712010514.55274.david@vizion2000.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Dec 01, 2007 at 05:14:55AM -0800, David Southwell wrote: > On Saturday 01 December 2007 Pav Lucistnik <pav@freebsd.org> answered par= t of=20 > the question: > > On Friday 30 November 2007 21:47:07 Jason C. Wells wrote: > > > Peter Jeremy wrote: > > > > On Fri, Nov 30, 2007 at 03:04:14PM -0600, Mark Linimon wrote: > > > >> On Fri, Nov 30, 2007 at 07:50:02AM -0800, Jason C. Wells wrote: > > > >>> It wouldn't surprise me if portmanager is hoping that KDE 4.0 wil= l go > > > >>> prime time real soon. That's my big conspiracy theory. > >> > >> > >> > >> package builds out the door. The Razor, and past experience, wou= ld > >> > >> suggest that sweeping changes would delay all that significantly. > >> > > > >> > > As a corollary, KDE4 will not hit the ports tree until after 7.0 a= nd > >> > > 6.3 are released. > .> > > >> > We lucked out last time and got current updates of both gnome and kd= e. > >> > > >> > "It would be a pleasant surprise if portmgr were able to take KDE 4.= 0 to > >> > prime time real soon." > >> > > >> > Later, > >>>Jason > >> > _______________________________________________ > >> > >> I must say I am having difficulty understanding the policies applicable > >> during ports freeze. > >> > > What criteria are used to determine whether an update is allowed or bar= red > > during the freeze? >=20 > Pav Lucistnik <pav@freebsd.org> answered part of the question with this= =20 > interjection: >=20 > >David Southwell p=ED??e v so 01. 12. 2007 v 03:08 -0800: >=20 > >> What criteria are used to determine whether an update is allowed or ba= rred=20 > >> during the freeze?=20 >=20 > >1) Security update > >2) Build fix on one of the release platforms > >3) Major runtime fix > > >=20 > This seems sensible unless: > a) The freeze is unduly long (I would suggest more than two weeks) > AND > b) There is a major upgrade of a port which is used by a large proportion= of=20 > users. AND c) The upgrade is very unlikely to break things. An upgrade to KDE or Gnome or X.org or similarily gargantuan ports (or many smaller ports too for that matter) fail point c). >=20 > In which case I believe such major upgrades should be favourably consider= ed.=20 > Such a policy would reflect the fact that there are many users who need t= o=20 > keep their systems up to date (especially when they workin communities wh= ere=20 > multiple operating systems are in use). Allowing port freezes to extend f= or=20 > long periods should not IMHO be allowed to conflict with the need to keep= =20 > major ports updated. The ports freeze is intended to make sure the ports tree is in a stable and well tested state for the release. Updating major ports always carry a great risk of breaking things thus defeating the point of the freeze. >=20 > This puts added weight to my second question to which I am hoping for so= me=20 > response: > >> The freeze seems to be of longer duration than originally expected whi= le > >> the current inconvenience seems to growing exponentially. I appreciate= the > >> long term benefits so please do not think I am in any way critical of = those > >> who are working on this. > >> > >> I would hgowever like to ask, on the basis of what is being learned no= w, > >> how could the length freezes be diminished on future occasions? > >> --=20 <Insert your favourite quote here.> Erik Trulsson ertr1013@student.uu.se
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20071201132508.GA33039>