Draft of Scribus Release Checklist: Difference between revisions

From Scribus Wiki
Jump to navigation Jump to search
(Redirect)
 
(One intermediate revision by the same user not shown)
Line 1: Line 1:
[[Category:Development]]
#REDIRECT [[Release_management]]
 
'''''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==
# Feature freeze
# E-mail to the mailing list announcing the feature freeze and asking for testing
 
==Release Day - 2 weeks==
# String freeze
# Bump translation files (use Tansifex script --push flag to refresh all translation langs on Transifex)
# 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==
# 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==
# 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===
# Pull Translations from Transifex using the script --pull option (which will pull all Transifex maintained languages)
 
===After Release===
# Release announcement to the mailing list
# Unleash the translators, asking them to send their translated release announcements to local  media

Latest revision as of 22:43, 14 November 2016

Redirect to:

Retrieved from "https://wiki.scribus.net/wiki/index.php?title=Draft_of_Scribus_Release_Checklist&oldid=33735"