Date: Fri, 12 Dec 2008 15:51:45 -0500 From: Jerry <gesbbb@yahoo.com> To: freebsd-questions@freebsd.org Subject: Re: Release schedules Message-ID: <20081212155145.1618810a@scorpio> In-Reply-To: <f2c294a10812121220r78835060n5ed756051e92d916@mail.gmail.com> References: <200811121259.25046.jonathan%2Bfreebsd-questions@hst.org.za> <20081112120147.GA62386@slackbox.xs4all.nl> <f2c294a10812120920l4d11bebfgd5c9208336b075b@mail.gmail.com> <18754.42851.295211.155980@jerusalem.litteratus.org> <4ad871310812121028m4e368da4n69e06d592e312eb0@mail.gmail.com> <26ddd1750812121113o1590d54r9962ec3d22a20bdb@mail.gmail.com> <4ad871310812121128y18db1c19n8aa45dcc75794739@mail.gmail.com> <26ddd1750812121149r6581ace1gec21e415afe3deca@mail.gmail.com> <f2c294a10812121220r78835060n5ed756051e92d916@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--Sig_/=WCke=U9b+O.eosTAAQbPbW Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On Fri, 12 Dec 2008 12:20:12 -0800 "Joe S" <js.lists@gmail.com> wrote: >On Fri, Dec 12, 2008 at 11:49 AM, Maxim Khitrov <mkhitrov@gmail.com> >wrote: >> On Fri, Dec 12, 2008 at 2:28 PM, Glen Barber >> <glen.j.barber@gmail.com> wrote: >>> On Fri, Dec 12, 2008 at 2:13 PM, Maxim Khitrov <mkhitrov@gmail.com> >>> wrote: >>>> For example, RC2 builds were scheduled for 29 September 2008. When >>>> that day comes (or same week perhaps), whoever has the ability to >>>> change the release schedule page should update it regardless of >>>> what happened. If RC2 builds started, that should be reflected in >>>> the 'actual' column. Otherwise, if it's a minor change in the >>>> timeline, put the new expected date in. As is the case of 7.1 >>>> release, if the person honestly has no idea when RC2 will happen, >>>> put in 'December', 'January', 'Second half of January'... >>>> 'Sometime next year' if it's that uncertain. Anything at all; it >>>> takes 5 minutes to do. In the worst case, your estimate will need >>>> to be updated again in a month or two. In the best case, the >>>> release will be made before the expected date. I, for one, promise >>>> not to complain about that. :) >>>> >>> >>> If the sacrifice is an out-of-date column in a webpage while bugs >>> are being worked out, in my opinion, that's fine with me. (IMHO) >> >> My point was that it shouldn't be one or the other. Taking a few >> minutes to update the web page does not interfere with the debugging >> process. It also doesn't force developers to follow that timeline. It >> is simply an indication to the users what their expectations should >> be at the present time. >> >> - Max > >Again, I wonder if the reason for the delays is that too much work is >being taken on for each release. I agree that FreeBSD should be >released when it is done and quality is of utmost importance. Perhaps >it would be better to focus on adding a few less features than >planned, so that they can be implemented well and on time. > >I admit, I am not part of the project, and in the end, I have no idea >what's going on. I just know that other projects with FAR less >developers have found a way to do this, so it's not *that* hard. My biggest gripe with the entire update schedule is that the ports freeze has been frozen longer than my wife. Maybe having two separate ports, one for the current version and one for the RC? version might work better. I have never fully understood why the ports had to be frozen anyway. Why can there not be two separate entities, the current version and the beta one? --=20 Jerry gesbbb@yahoo.com Many a bum show has been saved by the flag. George M. Cohan --Sig_/=WCke=U9b+O.eosTAAQbPbW Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (FreeBSD) iEYEARECAAYFAklCzuIACgkQBvaKIJWWCO3ePACbBga2a+pf5AJlGZqYSImU7Gpc 0ugAoKR4aOxIskYXYoHMhF6+1wABFsaj =kWpp -----END PGP SIGNATURE----- --Sig_/=WCke=U9b+O.eosTAAQbPbW--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20081212155145.1618810a>