Hi! Reading some of the latest blog entries today, I've seen there has been some (newbie) user frustration with the latest X.org upgrade (mostly by not reading docs or not understanding the ports system at all). flz@ and des@ had a lot of trouble with some guys. Currently, if a new user is trying out FreeBSD, he will most likely set up a 6.2-RELEASE system and end up in the X.org upgrade war. As a new user is most likely not prepared to manage the system at all, he will most likely probe FreeBSD being unmaintainable (as he will most likely not know how to deal with ports at all). While reading about all that latest trouble, I think it might not be a bad idea to have a (quick) release cycle and release something like 6.2.1-RELEASE (6.3 is still TBA). I'm considering the latest X.org upgrade being a major upgrade which would justify a release cycle (@ flz: you did a great job). That would keep the trouble from new users and also from some mailing lists. I know there's a release cycle for 7-CURRENT planned next June but IMHO it can be delayed for some weeks. What does the core and releng team think? It might do good. Just my 2ct. Volker
On 5/29/07, Volker <volker@vwsoft.com> wrote:> Hi!<snip>> While reading about all that latest trouble, I think it might not be a > bad idea to have a (quick) release cycle and release something like > 6.2.1-RELEASE (6.3 is still TBA). I'm considering the latest X.org > upgrade being a major upgrade which would justify a release cycle (@ > flz: you did a great job). That would keep the trouble from new users > and also from some mailing lists. > > I know there's a release cycle for 7-CURRENT planned next June but > IMHO it can be delayed for some weeks. > > What does the core and releng team think? It might do good. > > Just my 2ct. > > VolkerVoker, I think with ports freeze still the case, they can't release a new version before sorting all Xorg 7.2 issues IMHO. -- Regards, -Abdullah Ibn Hamad Al-Marri Arab Portal http://www.WeArab.Net/
On Tue, May 29, 2007 at 11:45:15AM +0200, Volker wrote:> Hi! > > Reading some of the latest blog entries today, I've seen there has > been some (newbie) user frustration with the latest X.org upgrade > (mostly by not reading docs or not understanding the ports system at > all). flz@ and des@ had a lot of trouble with some guys. > > Currently, if a new user is trying out FreeBSD, he will most likely > set up a 6.2-RELEASE system and end up in the X.org upgrade war. As a > new user is most likely not prepared to manage the system at all, he > will most likely probe FreeBSD being unmaintainable (as he will most > likely not know how to deal with ports at all).A new user setting up a 6.2-RELEASE system will most likely use the packages and/or the ports tree that shipped with 6.2-RELEASE. The X.org upgrade will only be a concern to such a user *if* he upgrades his ports tree. Most new users will likely not know how to do that.> > While reading about all that latest trouble, I think it might not be a > bad idea to have a (quick) release cycle and release something like > 6.2.1-RELEASE (6.3 is still TBA). I'm considering the latest X.org > upgrade being a major upgrade which would justify a release cycle (@ > flz: you did a great job). That would keep the trouble from new users > and also from some mailing lists. > > I know there's a release cycle for 7-CURRENT planned next June but > IMHO it can be delayed for some weeks. > > What does the core and releng team think? It might do good.A quick release cycle for a release from -STABLE sounds like a bad idea. There have been enough new things that have gone into the 6-STABLE branch that a full release cycle seems warranted. I also think that it would be a bad idea to create *any* new release until after the X.org upgrade has settled down - it has not done that quite yet as far as I can tell. -- <Insert your favourite quote here.> Erik Trulsson ertr1013@student.uu.se
On 2007-May-29 12:29:29 +0200, Erik Trulsson <ertr1013@student.uu.se> wrote:>A quick release cycle for a release from -STABLE sounds like a bad idea. >There have been enough new things that have gone into the 6-STABLE branch >that a full release cycle seems warranted.Agreed. 6.3-RELEASE would nominally be due around July but the lack of any schedule on http://www.freebsd.org/releng/ suggests that it will be later than that. The plans to start the 7.0-RELEASE cycle will also impact this.>I also think that it would be a bad idea to create *any* new release until >after the X.org upgrade has settled down - it has not done that quite yet >as far as I can tell.Given the size of the upgrade, I think it has gone very smoothly, though there _are_ a few rough edges. A few weeks to a month should shake things out. -- Peter Jeremy -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 187 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20070529/713c7ed1/attachment.pgp
On Tue, May 29, 2007 at 09:17:57PM +1000, Peter Jeremy wrote:> Agreed. 6.3-RELEASE would nominally be due around July but the lack > of any schedule on http://www.freebsd.org/releng/ suggests that it will > be later than that. The plans to start the 7.0-RELEASE cycle will also > impact this.At BSDCan, Ken Smith mentioned that 7.0 is due to be branched in July and released in Aug/Sep, with 6.3 quickly following (perhaps even overlapping so as to reuse the same ports freeze). The ports tree is not even close to stable enough to release right now. mcl
On 29/05/07, Mark Linimon <linimon@lonesome.com> wrote:> On Tue, May 29, 2007 at 09:17:57PM +1000, Peter Jeremy wrote: > > Agreed. 6.3-RELEASE would nominally be due around July but the lack > > of any schedule on http://www.freebsd.org/releng/ suggests that it will > > be later than that. The plans to start the 7.0-RELEASE cycle will also > > impact this. > > At BSDCan, Ken Smith mentioned that 7.0 is due to be branched in July and > released in Aug/Sep, with 6.3 quickly following (perhaps even overlapping > so as to reuse the same ports freeze). > > The ports tree is not even close to stable enough to release right now. > > mcl > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" >Given that Kris repeatedly tells me and others that the ports system is only supported on the latest freebsd release (meaning one has to be upgrading freebsd on their servers every few months to get this support) if 7.0 and 6.3 are released around the same time will the ports tree be supported on both? Due to the fact the ports tree is only supported on the latest freebsd release I propose longer release cycles for example not releasing 6.3 until 6.2 is almost EOL rather then having 2 releases overlap each other because the current situation is there is a release that is supported by the security team but not by the ports tree so it is a half supported release, I also prefer slower major release cycles as well but I keep been told no on that one :) eg. it would be nice if 7.0 was delayed a month or more to allow the full pf openbsd synch up rather then leaving it because lack of time before 7.0 release. Chris Chris
Chris <chrcoluk@gmail.com> wrote:> On 29/05/07, Mark Linimon <linimon@lonesome.com> wrote: > > On Tue, May 29, 2007 at 09:17:57PM +1000, Peter Jeremy wrote: > > > Agreed. 6.3-RELEASE would nominally be due around July but the lack > > > of any schedule on http://www.freebsd.org/releng/ suggests that it will > > > be later than that. The plans to start the 7.0-RELEASE cycle will also > > > impact this. > > > > At BSDCan, Ken Smith mentioned that 7.0 is due to be branched in July and > > released in Aug/Sep, with 6.3 quickly following (perhaps even overlapping > > so as to reuse the same ports freeze). > > > > The ports tree is not even close to stable enough to release right now.> Given that Kris repeatedly tells me and others that the ports system > is only supported on the latest freebsd release (meaning one has to be > upgrading freebsd on their servers every few months to get this > support) if 7.0 and 6.3 are released around the same time will the > ports tree be supported on both?I believe you misunderstood something. Where do you think Kris said that? Fabian -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 187 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20070602/f6feb6a0/signature.pgp
On 02/06/07, Fabian Keil <freebsd-listen@fabiankeil.de> wrote:> Chris <chrcoluk@gmail.com> wrote: > > > On 29/05/07, Mark Linimon <linimon@lonesome.com> wrote: > > > On Tue, May 29, 2007 at 09:17:57PM +1000, Peter Jeremy wrote: > > > > Agreed. 6.3-RELEASE would nominally be due around July but the lack > > > > of any schedule on http://www.freebsd.org/releng/ suggests that it will > > > > be later than that. The plans to start the 7.0-RELEASE cycle will also > > > > impact this. > > > > > > At BSDCan, Ken Smith mentioned that 7.0 is due to be branched in July and > > > released in Aug/Sep, with 6.3 quickly following (perhaps even overlapping > > > so as to reuse the same ports freeze). > > > > > > The ports tree is not even close to stable enough to release right now. > > > Given that Kris repeatedly tells me and others that the ports system > > is only supported on the latest freebsd release (meaning one has to be > > upgrading freebsd on their servers every few months to get this > > support) if 7.0 and 6.3 are released around the same time will the > > ports tree be supported on both? > > I believe you misunderstood something. Where do you think Kris said that? > > Fabian > >He said using the ports is only supported in the latest FreeBSD release, so eg. its not supported in 5.5 and 6.0 and 6.1. Chris