ReleaseTasks

These tasks need to be done for an Opie release:

 Before the release, ensure all bugs are either fixed or deferred. A few weeks before the projected release date, announce that the repository is frozen and only critical bugfixes should be added. Ensure the ChangeLog is up-to-date (refer to the release master bug and git history) Update  - there are two fields to change,   (text) and   (numeric) and commit it. Tag the repository using  with a version tag, eg.   for version 1.2.5. Create a tarball of the git repository state using the following command: git archive HEAD | gzip > opie-1.2.5.tar.gz  Prepare a release announcement email message. Refer to previous announcements (see mailing list archives) for content/structure. Upload the source tarball to the Sourceforge release system</li> Update the OpieHistory page</li> Upload a new ChangeLog file to docs/ on the website</li> Update OpenEmbedded recipes in meta-opie</li> Send the announcement to various places (TODO: details, see Opie124ReleasePlan for now)</li> Add the new version to the bug tracker (under Manage -> Manage Projects -> OPIE -> Versions).</li> Update #opie IRC channel topic on freenode</li> Update  -   should be   where   is still the version just released, and commit it.</li> Announce on opie-devel that the git tree is open for commits again (?)</li> </ol>