Am 10/26/2015 10:47 PM, schrieb Andrea Pescetti:
On 26/10/2015 Marcus wrote:
nice plan, haven't seen this before - but maybe I've just overlooked the
link in previous mails.
(Note: our messages crossed, so I had some wrong information in my
previous mail). Yes, the page has been there for a while, with regular
updates. Actually you got even credited since it is based on your
earlier work on release planning pages!
ah, nice to know :-)
1) Preparing Release Notes. I've already updated
https://cwiki.apache.org/confluence/display/OOOUSERS/AOO+4.1.2+Release+Notes
but it still needs work. I can take care of it.
Do you mean some more translations or specific things in the English
text?
No, I meant that most of it was still generic text, which I have now
replaced with 4.1.2-specific information.
2) Upload to mirrors. Does anyone know how to copy files to SF, and how
long it takes? If it is a lengthy operation I'd rather start it soon. If
anyone is available, please step forward.
Juergen has done this in the past (IMHO). So, maybe he tell you at least
if it was a slow task.
OK. I thought you had done it. But I've now logged in on SourceForge and
I see that several OpenOffice PMC members have access, including you,
me, Juergen, Herbert, Gavin and others. So maybe I can simply start
copying the files myself.
Until now there are no real blockers and no veto vote. So, starting the
upload now shouldn't be wrong.
I remember that it's possible to set a staging bit at SourceForge for
the new 4.1.2 directory. Then it is not yet visible for the world and
nobody would see that is deleted again - if you see the need for
uploading again or new files.
3) Preparing the website. ...
Right, I've prepared already the main website locally. The localized
websites will come next. I can do the production update in the evening
hours (European time).
Good, thanks!
With regards to this I've updated the release schedule.
5) Enabling update notifications for 4.1.1. This can come gradually.
To keep the download peak and therefore the load in the first days a bit
lower, IMHO it's better to enable them a bit splitted - e.g., the
Windows builds 1 week after the release, everything else 2 weeks after
the release.
I agree. Priority should go to the English website, then localized
websites, then updates (actually, there isn't a big difference between
enabling updates for Windows and enabling them for all operating systems).
OK, then we have the chance to differenciate between the languages to
stretch the notifications over 2 weeks.
Marcus
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org
