You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

The purpose of the following table is to provide a schedule plan for a new release planning.

It is desired for a new major release (x.y like 4.1) but it could be also used for a minor release (x.y.z like 4.1.1).

 

Important:

Please do not fill the template with data for a new release but copy & paste it and create a new page.

 

Phases and steps in scheduleDateResponsibleComment
Feature freeze   
  • Start
?Committer 
  • Announce it on dev@, qa@, l10n@
?Release Manager 
  • Create Release Notes (RN) in Confluence Wiki
?Committer 

Translation phase

   
  • Start
?NL community 
  • End
?NL community 
  • Announce it on dev@, qa@, l10n@
?Release Manager 

String freeze

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

Translation phase

   
  • Start
?NL community 
  • End
?NL community 
  • Announce it on dev@, qa@, l10n@
?Release Manager 

Code freeze

   
  • Start
?Committer 
    • Start release blocker mod
?Release Manager 
    • Update RN with latest changes
?All people 
    • Announce it on dev@, qa@, l10n@
?Release Manager 

Translation phase

   
  • Start
?

NL community

 
  • End
?NL community 
  • Announce it on dev@, qa@, l10n@
?Release Manager 
Beta Release   
  • 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
    • See [1] for details
?Committer 
  • Reminde the release blocker mode
    • Announce it on dev@, qa@, l10n@
?Release Manager 
Release Candidate   
  • 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

   
  • 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] 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 BZ
    • Add/modify values for:
    • "Version", "Target milestone", "Release blocker flag"
?BZ Admin 
  • Update version / milestone / build ID data in SVN
    • e.g., "4.2.0" --> "4.3.0"
?Developer 
  • Update "w.oo.o" homepage
    • Create new blog and/or news entry
    • Update headline below the logo
?Committer 
  • Create a "kid" build for translation testing
?Release Manager 
    • Announce it on dev@, qa@, l10n@
?Release Manager 
  • No labels