On Mon, Sep 16, 2013 at 4:44 AM, Henk P. Penning <penn...@uu.nl> wrote: > On Sat, 14 Sep 2013, Andrea Pescetti wrote: > >> Date: Sat, 14 Sep 2013 17:19:32 +0200 >> From: Andrea Pescetti <pesce...@apache.org> >> To: Henk P. Penning <penn...@uu.nl> >> Cc: dev@openoffice.apache.org >> >> Subject: Re: 4.0.1 release and distribution. > > >> Everything was OK in the 4.0 case. > > > No. Regarding the mirrors, it was not ok. > > Fact : 4.0.1 will be put on the mirrors in 4-5 days, adding some > languages every day. That is a technical constraint. > > Fact : if AOO announces "too soon", /all/ mirrors will be incomplete. > > I'm not discussing here, or looking for a compromise ; I'm telling > you how it is. > > AOO can either "do it right" (by waiting a few more days), or not. >
My impression was the only mandatory part of a release was the source tarballs and associated signatures and hashes. These are few and small and should not require special handling. The "convenience binaries" are optional in an Apache release. (Some even argue that they are not part of the release at all.) We predominately publish these binaries via SourceForge. Very few get these from the Apache mirrors. But we did receive several requests after the 4.0 release to push these binaries onto the mirrors. (We receive even more requests to put them our as BitTorrents) I'm hoping that there is some way that we can avoid a secondary distribution mechanism from causing a delay in our primary distribution mechanism. Maybe we can resolve this on the website? Don't list links to the ASF mirrors at initial release. Just give the SourceForge links. Then after 4-5 days, after we've verified replication, we modify the website to also point to the ASF mirrors? This gives four stages: Stage 1: Distribute source tarballs, hashes and signatures to Apache mirrors. Wait the usual 24 hours. In parallel replicate the binaries over to SourceForge. Stage 2: After the Apache mirrors and SourceForge have their files, then we announce. Website only links to Apache mirrors for source and hash/signatures. Release announcement happens now. Stage 3: We then push out the binaries to the Apache mirrors. We don't start this earlier because we want to prioritize the replication of the source, hashes and signatures. Stage 4: After 4-5 days we update website to point to Apache mirrors as alternate download site for binaries. Would that work? -Rob > >> Andrea. > > > Regards, > > Henk Penning > > ------------------------------------------------------------ _ > Henk P. Penning, ICT-beta R Uithof BBL-761 _/ \_ > Faculty of Science, Utrecht University T +31 30 253 4106 / \_/ \ > Princetonplein 5, 3584CC Utrecht, NL F +31 30 253 4553 \_/ \_/ > http://www.staff.science.uu.nl/~penni101/ M penn...@uu.nl \_/ > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
