On Sun, 1 Sep 2013, Rob Weir wrote:
Date: Sun, 1 Sep 2013 15:31:37 +0200
From: Rob Weir <robw...@apache.org>
To: "dev@openoffice.apache.org" <dev@openoffice.apache.org>
Cc: janI <j...@apache.org>, Henk P. Penning <penn...@uu.nl>
Subject: Re: 4.0.1 release and distribution.
On Sun, Sep 1, 2013 at 5:42 AM, janI <j...@apache.org> wrote:
On 1 September 2013 11:27, janI <j...@apache.org> wrote:
Hi.
I had a talk on #asfinfra today, regarding our upcomming 4.0.1 release.
Sync on mirrors takes about a week, and the mirror can in general not hold
4.0 and 4.0.1
Is this a change? The current published advice is that the mirrors
take no more than 24 hours to sync:
AOO is special, being 22+ GB.
For 4.0.0 I added the binaries slowly ; some 4 to 5 languages
a day is what the rsync servers can handle. So, it takes 5 days
for the quick mirrors plus 2 days for the straglers. Note that
there are some sites that are still trying to catch up.
Soon after GA date (or earlier), refs to 4.0.0 sigs and sums should
point to 'archive.apache.org/' (instead of www.apache.org).
https://www.apache.org/dev/release-publishing.html#distribution
Therefore the current suggestion is to
a) remove 4.0 from mirrors GA - 1week = 12 september
b) update 4.0.1 to mirrors GA = 19 september.
The downside is that mirrors will have the 4.0 ready for download for upto
a week.
The problem is we don't know for certain a GA date a week in advance.
We can just estimate. But as we saw with 4.0.0, a last minute defect
can delay things by a week or more.
So in practice this means that there could be more than a week where
4.0.0 is not on the mirrors. Maybe this is not a problem?
I can't judge that ; the problem is that by GA date the sigs/sums
have to be in /dist/ ; it complicates matters if by GA date
/dist/ isn't completely available for the mirrors ; the XXX.sigs
etc would have to be copied into /dist/ separately from the XXX's.
The two things to watch out for (and you have probably already
considered these, but I'll mention them just in case):
1) We should not remove the 4.0.0 hashes and signature files from
/dist. These are referenced even when the binaries are downloaded
from SourceForge.
"remove from the mirrors" is done by excluding 4.0.0 in rsyncd.conf ;
that is, stuff will be in /dist/, but mirrors will think it's gone.
2) We need to make sure SourceForge is not rsyncing from /dist and
mirror the 4.0.0 removal.
Rsyncs on SF are done "by hand". When the entire 4.0.1 is ready,
it should sit somehere (outside /dist/), say XXX ; SF will pick
up XXX with a custom rsync module ; XXX will by copied in parts
to /dist/.
And I assume 4.0.1 goes to archive then?
yep.
-Rob
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
