Repository : ssh://git@open-mesh.org/doc

On branches: backup-redmine/2017-07-13,master

commit 661208f990b67f7746ffd7d67ab40e92bb4e3c97 Author: Marek Lindner mareklindner@neomailbox.ch Date: Sun Jan 30 15:30:15 2011 +0000

doc: batman-adv/Release-todo

661208f990b67f7746ffd7d67ab40e92bb4e3c97 batman-adv/Release-todo.textile | 66 +++++++++++++++++++++-------------------- 1 file changed, 34 insertions(+), 32 deletions(-)

diff --git a/batman-adv/Release-todo.textile b/batman-adv/Release-todo.textile index 93c50d24..1e6f8534 100644 --- a/batman-adv/Release-todo.textile +++ b/batman-adv/Release-todo.textile @@ -1,53 +1,55 @@ -== Release Checklist == + +h2. Release Checklist +

This page contains a checklist of things that need to be done for a release.

-'''Release Scheduling''' +*Release Scheduling*

[[Image(wiki:release-todo:release_scheduling.svg)]]

- * next branch is released as feature release 20_ _.a.0 after linux 2.6.x-rc3 is tagged - * maint branch is released on demand (for example after security issues) - * a feature release __must__ be done before 2.6.x-rc6. The time till 2.6.x-rc7 is needed to merge new features into next and submit them to the linux maintainers for 2.6.y +* next branch is released as feature release 20_ _.a.0 after linux 2.6.x-rc3 is tagged +* maint branch is released on demand (for example after security issues) +* a feature release +must+ be done before 2.6.x-rc6. The time till 2.6.x-rc7 is needed to merge new features into next and submit them to the linux maintainers for 2.6.y

-'''Code''' +*Code*

- * [x] make sure all code contains the release version strings - * [x] update copyright years (if needed) - * [x] remove dead code (if any) - * [x] check against kernel versions - * [x] check that maint branch is merged in next - * [x] check for open patches on the ml - * [x] git tag release +* [x] make sure all code contains the release version strings +* [x] update copyright years (if needed) +* [x] remove dead code (if any) +* [x] check against kernel versions +* [x] check that maint branch is merged in next +* [x] check for open patches on the ml +* [x] git tag release

-'''Documentation''' +*Documentation*

- * [x] build changelog - * [x] update README - * [x] write release announcement - * [x] update wiki documentation +* [x] build changelog +* [x] update README +* [x] write release announcement +* [x] update wiki documentation

-'''Release''' +*Release*

- * [x] build package tar.gz and generate checksums - * [x] move packages/checksums to stable/sources / create symlinks from releases - * [x] update download links in the trac downloads page - * [x] send release mail - * [x] update IRC channel topic +* [x] build package tar.gz and generate checksums +* [x] move packages/checksums to stable/sources / create symlinks from releases +* [x] update download links in the trac downloads page +* [x] send release mail +* [x] update IRC channel topic

-'''Distributions''' +*Distributions*

- * [x] update openwrt package - * [x] update debian package +* [x] update openwrt package +* [x] update debian package

-'''Aftershow''' +*Aftershow*

- * [x] Merge differences (README, CHANGELOG, ...) into master branch - * [x] Merge current next into maint (must be fast-forward or pre-tagging steps were done wrong) - * [x] Get patches for next release from master-rebase/batctl-rebase repository - * [x] Rebase patches in next on top of linux-next and send it to kernel maintainers for future kernels +* [x] Merge differences (README, CHANGELOG, ...) into master branch +* [x] Merge current next into maint (must be fast-forward or pre-tagging steps were done wrong) +* [x] Get patches for next release from master-rebase/batctl-rebase repository +* [x] Rebase patches in next on top of linux-next and send it to kernel maintainers for future kernels