Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Phases and steps in scheduleDateResponsibleComment
Feature freeze   
  • Start
?Committer 
  • Announce it on dev@, qa@, l10n@
?Release Manager 
  • Update version / milestone / build ID data in SVN
    • e.g., "4.1.0" --> "4.2.0"
?Developer 
  • Create new branch in SVN for the new release
?Developer 
  • Create Release Notes (RN) in Confluence Wiki
?Committer 

String freeze

   
  • Start
?NL community 
    • Update RN with new languages
?Release Manager 
    • Announce it on dev@, qa@, l10n@
?Release Manager 

Translation phase

   
  • Changes in strings for the application UI and Help as well as for dictionaries
   
  • Start
?NL community 
  • End
?NL community 
  • Announce it on dev@, qa@, l10n@
?Release Manager 

Code freeze

   
  • Start
?Committer 
    • Start release blocker mode (aka show stopper mode)
?Release Manager 
    • Commit changes to reflect the upcoming release:
      • Version number, build ID, build date+time, copyright year
?Release Manager 
    • Update all bundled dictionaries
?L10N list 
    • Update RN with latest changes
?All people 
    • Announce it on dev@, qa@, l10n@
?Release Manager 
Beta ReleaseDateResponsibleComment
  • Build the RC
?Release Manager 
?Release Manager 
  • Start vote
?Release Manager 
  • Announce vote on dev@, qa@, l10n@
?Release Manager 
  • Start Beta testing phase
?QA 
  • Update RN with latest changes
?All people 
  • Start translating RN
?NL community 
  • Announce it on dev@ (+ qa@, l10n@)
?Release Manager 
  • End Beta testing phase
?QA 
  • Announce vote results on dev@ (+ qa@, l10n@)
?Release Manager 
  • Upload files to Apache Dist/SourceForge
    • Make sure to set the staging bit for the Beta directory
?Release Manager 
  • Update download scripting  – javascript  files in /download
    • See [1] in the next table below for details
?Committer 
  • Remind the release blocker mode
    • Announce it on dev@, qa@, l10n@
?Release Manager 
Release CandidateDateResponsibleComment
  • Build the RC
?Release Manager 
  • Update Wiki page to make the files available
?Release Manager 
  • Start vote
?Release Manager 
  • Announce vote on dev@, qa@, l10n@
?Release Manager 
  • Start RC testing phase
?QA 
  • Update RN with latest changes
?All people 
  • Update translating RN
?NL community 
  • Announce it on dev@ (+ qa@, l10n@)
?Release Manager 
  • End RC testing phase
?QA 
  • End vote (date *and* time in UTC timezone)
?Release Manager 
  • Announce vote results on dev@ (+ qa@, l10n@)
?Release Manager 

General Availability

DateResponsibleComment
  • Prepare
   
    • Upload files to Apache Dist/SourceForge
      • Make sure to set the staging bit for the RC directory
?Release Manager 
    • Update download scripting
      • See [2] in the next table below for details
?Committer 
    • Verify RN if all is correct
?All people 
  • Public Announcement of GA
    • Announce it on announce@, dev@
?Release Manager 

After release job

   
  • Update data in Bugzilla:
    • Add/modify values for:
      • "Version", "Target milestone", "Release blocker flag", "Last Confirmation on"
?BZ Admin 
  • Update version / milestone / build ID data in SVN:
    • e.g., "4.1.0" --> "4.2.0"
?Developer 
  • Update "www.openoffice.org" homepage:
    • Create new blog and/or news entry
    • Update news entry on homepage
    • Update headline below the logo
?Committer 
?Committer 
  • Create a "kid" build:
    • This helpful and often asked for translation testing.
    • Announce it on dev@, qa@, l10n@
?Release Manager 

...