Draft of Scribus Release Checklist: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
| Line 1: | Line 1: | ||
[[Category:Scribus_development]] | [[Category:Scribus_development]] | ||
'''''Please, Scribus core team devs, add your remarks/proposals for this release checklist''''' | |||
=How to Prepare a Scribus Release= | =How to Prepare a Scribus Release= | ||
Revision as of 11:17, 28 March 2007
Please, Scribus core team devs, add your remarks/proposals for this release checklist
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
- 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
After Release
- Release announcement to the mailing list
- Unleash the translators, asking them to send their translated release announcements to local media