Draft of Scribus Release Checklist: Difference between revisions

From Scribus Wiki
Jump to navigation Jump to search
mNo edit summary
m (Text replace - "Category:Scribus_development" to "Category:Development")
Line 1: Line 1:
[[Category:Scribus_development]]
[[Category:Development]]


'''''Please, Scribus core team devs, add your remarks/proposals for this release checklist (please keep it simple, it should be easy to print and follow for everybody involved in the release making routine)'''''
'''''Please, Scribus core team devs, add your remarks/proposals for this release checklist (please keep it simple, it should be easy to print and follow for everybody involved in the release making routine)'''''

Revision as of 23:52, 20 December 2010


Please, Scribus core team devs, add your remarks/proposals for this release checklist (please keep it simple, it should be easy to print and follow for everybody involved in the release making routine)

How to Prepare a Scribus Release

Release Day - 3 weeks

  1. Feature freeze
  2. E-mail to the mailing list announcing the feature freeze and asking for testing

Release Day - 2 weeks

  1. String freeze
  2. Send an e-mail to all Scribus translators and to the mailing list about the deadline of the upcoming release -- set the deadline for delivering the translations to e.g. "Release Day -1 day"

Release Day - 1 week

  1. Send the final version of the (short) release announcement to all translators, asking them to translate it into their languages -- set the deadline for delivering the translations to e.g. "Release Day -1 day"

Release Day - 3 days

Release Day - 2 days

Release Day - 1 day

  1. E-mail to all Scribus translators and to the mailing list that the deadline for their translations is about to pass

Release Day

Before Release

After Release

  1. Release announcement to the mailing list
  2. Unleash the translators, asking them to send their translated release announcements to local media