From dev-return-38618-apmail-openoffice-dev-archive=openoffice.apache.org@openoffice.apache.org Mon Jul 15 14:11:15 2013 Return-Path: X-Original-To: apmail-openoffice-dev-archive@www.apache.org Delivered-To: apmail-openoffice-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id DECDA10EBB for ; Mon, 15 Jul 2013 14:11:14 +0000 (UTC) Received: (qmail 45485 invoked by uid 500); 15 Jul 2013 14:11:10 -0000 Delivered-To: apmail-openoffice-dev-archive@openoffice.apache.org Received: (qmail 45388 invoked by uid 500); 15 Jul 2013 14:11:10 -0000 Mailing-List: contact dev-help@openoffice.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@openoffice.apache.org Delivered-To: mailing list dev@openoffice.apache.org Received: (qmail 45368 invoked by uid 99); 15 Jul 2013 14:11:09 -0000 Received: from minotaur.apache.org (HELO minotaur.apache.org) (140.211.11.9) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 15 Jul 2013 14:11:09 +0000 Received: from localhost (HELO mail-pb0-f52.google.com) (127.0.0.1) (smtp-auth username robweir, mechanism plain) by minotaur.apache.org (qpsmtpd/0.29) with ESMTP; Mon, 15 Jul 2013 14:11:08 +0000 Received: by mail-pb0-f52.google.com with SMTP id xa12so11229686pbc.25 for ; Mon, 15 Jul 2013 07:11:08 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=LI6hd86xoTwS65/nU5fCVW9u9JrCdvgyYtNn3ixx824=; b=iKa5BBbFWNc7jZR1cwJeFM5e9FmqHdnsFJ6mlI4++CeBXCcwryecTd33lYk/FAeekr uwg9IyzVx2wavywscDuxpFK+QMgzWIZyWcpnfUT3ztPWQJe7c9zG6aglKjg6witeAgii 5PmfEqeknoC9E88ccHgI1QMB/ZcR65fe99zDCKcZxDr4DEu3SY45OZe9ed4/xfxmGEzv 7Hg71Nb8IOWz8ZmB9eIIectXztwkCnp3pdMbvCnagCQo9S7KseuCKNVXuW1MQb1+ln04 DY/A+OSF83g5Kh6SAKP2Q3hjVCLWTq3kDR/ogV5f6GokqnsPKzt7YS4/IWq3Amnt91uI PSPw== MIME-Version: 1.0 X-Received: by 10.67.21.229 with SMTP id hn5mr55864413pad.135.1373897468054; Mon, 15 Jul 2013 07:11:08 -0700 (PDT) Received: by 10.70.89.195 with HTTP; Mon, 15 Jul 2013 07:11:08 -0700 (PDT) Date: Mon, 15 Jul 2013 10:11:08 -0400 Message-ID: Subject: Coordination on AOO 4.0 Release Announcement From: Rob Weir To: "dev@openoffice.apache.org" , "marketing@openoffice.apache.org" , l10n@openoffice.apache.org Content-Type: text/plain; charset=UTF-8 As Juergen pointed out, the AOO 4.0 release vote has successfully completed. The release is approved. However, please *do not* go out and start announcing the release yet. We need to coordinate a few final steps before this is done, including: 1. Provisioning the files to the Apache and SourceForge distribution directories 2. Waiting for the files to replicate within the mirror network (as much as 24 hours) 3. Verify download scripts against actual AOO 4.0 files. 4. Complete the release notes. Convert them to HTML. Give some time for translations. 5. Prepare announcement emails and blog post and webpage. The above should all be done before we announce. After we announce, we have a few other items to do: 5. Update logos on social media sites 6. Enable update notification server 7. Follow up blog post +1 week. I'd like to recommend that we aim for a noon UTC announcement on Wednesday, if possible. That would mean that items 1-5 are complete then. Release notes translations can roll in over time if needed. But we should have the English Release Notes and the other items ready to go. Does this make sense? Am I missing anything? Anyone think that Wed. is not possible? It is better not to make an important announcement at the end of the week (Thursday or Friday) since that tends to mute the press coverage. We should use the Release Dashboard to coordinate the status of these items: https://cwiki.apache.org/confluence/display/OOOUSERS/4.0+Release+Dashboard Regards, -Rob --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org For additional commands, e-mail: dev-help@openoffice.apache.org