| 4 weeks |
1. Preparation |
|
Inform Association about release/schedule |
|
Check if a teaser blog post is required/create and get it approved before publishing. |
|
Are updates on django-cms.org required? - Teaser adoption / timeline / video update. |
|
Are documentation updates needed? - Tutorials, Official documentation (release notes). - Is the Changelog up-to-date, changes on the official documentation. |
|
Build and push translation strings to Transifex (see 2.2) |
|
Create announcement on Transifex |
| 2 weeks |
2. Release Candidate |
|
Publicly (and internally) announce code/feature freeze. |
|
Ask the community to contribute to new translations (IRC, G+, Twitter?). |
|
Write a blog post about the upcoming release. Get it approved before publishing. |
| -1 day |
3. Release Preparation |
|
Ensure blog post is up-to-date with changelog, etc. |
| Day 0 |
4. Gold Release |
|
Update the "download" button(s) on django-cms.org to point to the latest release |
|
Update content (Timeline, Video, Screenshots) |
| Day 1 |
Get the GO from marketing team for "public release" |
|
Publish the blog post. |
|
Tweet about the release, linking to blog post |
|
Post about the release on Google Groups linking to the blog post: django-users, django-cms, and django-cms-developers |
|
Plan / Send Newsletter |
|
Plan / Send Press Release |
|
Update other content such as Video / Texts on django-cms.org |
| Week 1 |
5. After the release is before the Release |
|
Hackernews post (ensure that we have around 300 demos ready) |
|
Update official Wiki page |
|
Maintain a close watch on django CMS email lists, IRC, Twitter, Stack Overflow etc. for recurring or serious problems |
|
Update public roadmap page |
HackMD
