Date: Mon, 9 Jan 2012 15:58:02 -0500 From: Arnaud Lacombe <lacombar@gmail.com> To: Freddie Cash <fjwcash@gmail.com> Cc: FreeBSD current mailing list <freebsd-current@freebsd.org> Subject: Re: stable/9 still looking for packages at 9-current Message-ID: <CACqU3MXsv9t4RwQoqZbe%2BB59jNUH6FVYtD5tk22NMqMsu6_%2Bxg@mail.gmail.com> In-Reply-To: <CAOjFWZ7AQbRbxZ%2Bquu-qEVOnRkp2v5zEr8ZLB7-HMZarS4NJNw@mail.gmail.com> References: <CACqU3MWpV37%2BmbycW83t2mfTKQXWS7FaD8DYVrXySMKwFeyaqw@mail.gmail.com> <20120109143726.GA3185@lonesome.com> <CACqU3MU=OmYDw9gVifWx2Y-mN_dxcS-4izJ732DXZ9rxp=miTA@mail.gmail.com> <CADLo838xcMuGLqeX976XoMZnJYc6OTFEmc5K6GSmWOem52o6JQ@mail.gmail.com> <CAOjFWZ7AQbRbxZ%2Bquu-qEVOnRkp2v5zEr8ZLB7-HMZarS4NJNw@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi, On Mon, Jan 9, 2012 at 1:40 PM, Freddie Cash <fjwcash@gmail.com> wrote: > On Mon, Jan 9, 2012 at 10:27 AM, Chris Rees <utisoft@gmail.com> wrote: >> On 9 January 2012 18:16, Arnaud Lacombe <lacombar@gmail.com> wrote: >>> ok, I'm a stupid lazy user (obviously)... While browsing the ftp, I >>> see 9.0 ISOs in a `releases' directory. Do you expect me to consult >>> freebsd-announce@, verify the signature of the announce, the hash of >>> the ISOs, etc. to consider that 9.0 has been released ? No, I see 9.0 >>> ISOs in a `releases' directory, I assume it has been released, >>> whatever your spreading process is. >>> >>> Btw, none of the CHECKSUMS files are signed on the FTP. >> >> Have you checked the website? The latest supported release is clearly >> specified, right in the middle of the home page. >> >> Please don't tell me you'd look in ftp before checking the website. =A0I >> think you're just looking to nitpick. > > And, which is worse: > =A01. =A0tag the release branch, build the ISOs, upload to main FTP > server, wait for the mirrors (FTP, CVS, SVN) to sync, then make the > official announcement which includes a few days/weeks where "the > release" is available but not official; or > =A02. =A0tag the release branch, build the ISOs, upload to main FTP > server, make the official announcement, user goes to their > favourite/closest mirror, and can't access the release since it hasn't > synced yet > 3. tag the release[0], build the ISOs, upload then to main FTP and mirrors but restrict visibility[0], announce the release, make the build visible everywhere. At worse, fall-back on #2 with peer-to-peer distribution. If some steps in that process do not exist, create them. - Arnaud > I think people would complain a hell of a lot more about 2 than they > currently do about 1. > > Yes, people upgrading via source will see X.Y-RELEASE before it's > officially announced on the website/mailing lists. =A0Yes, people > browsing ftp.freebsd.org will see X.Y-RELEASE ISOs before it's > officially announced. =A0Yes, some users will get confused by seeing > X.Y-RELEASE available before the official annoucements. > > But, that's a lot better than making an annoucement and having users > unable to use it since it's not available on their local mirrors. > > What's annoying, though, is that we have to go through this with every > ... single ... minor ... release. =A0It's not a hard concept, yet every > time there's a new release, people get confused by it. > > Is there something that could be done to make it more > streamlined/smoother? =A0Maybe, maybe not. =A0Depends. =A0You'd have to w= ant > to join the RE team to find out more about the current release/mirror > infrastructure. =A0:) =A0And then be willing to put in the time/effort to > improve it. =A0:D > > Does all of Arnaud's complaining and nit-picking constitute a request > to volunteer to "fix" things? =A0;) > > -- > Freddie Cash > fjwcash@gmail.com > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org= "
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CACqU3MXsv9t4RwQoqZbe%2BB59jNUH6FVYtD5tk22NMqMsu6_%2Bxg>