diff options
author | James Meyer <james.meyer@operamail.com> | 2009-03-14 04:07:05 (GMT) |
---|---|---|
committer | James Meyer <james.meyer@operamail.com> | 2009-03-14 04:07:05 (GMT) |
commit | c2941a012cbea19073e72af561b37a1255a1fe6c (patch) | |
tree | 168850edb01eea2168329eada8f2025bf3f21e23 /abs/core-testing/wlan-ng26-utils-svn/tmp/trunk/doc/releasepolicy.txt | |
parent | a501f7114b788b2879bab105ed4dcd7ed6a94f39 (diff) | |
download | linhes_pkgbuild-c2941a012cbea19073e72af561b37a1255a1fe6c.zip linhes_pkgbuild-c2941a012cbea19073e72af561b37a1255a1fe6c.tar.gz linhes_pkgbuild-c2941a012cbea19073e72af561b37a1255a1fe6c.tar.bz2 |
Remove wlan-ng26 as the drivers are now in the kernel.
Diffstat (limited to 'abs/core-testing/wlan-ng26-utils-svn/tmp/trunk/doc/releasepolicy.txt')
-rw-r--r-- | abs/core-testing/wlan-ng26-utils-svn/tmp/trunk/doc/releasepolicy.txt | 37 |
1 files changed, 0 insertions, 37 deletions
diff --git a/abs/core-testing/wlan-ng26-utils-svn/tmp/trunk/doc/releasepolicy.txt b/abs/core-testing/wlan-ng26-utils-svn/tmp/trunk/doc/releasepolicy.txt deleted file mode 100644 index b66a571..0000000 --- a/abs/core-testing/wlan-ng26-utils-svn/tmp/trunk/doc/releasepolicy.txt +++ /dev/null @@ -1,37 +0,0 @@ -linux-wlan Release Policy/Checklist --------------------------------------------------- - -[MSM Note: Here's a _quick_ attempt at a release policy for linux-wlan. - It's very brief and relatively simple. I'm open to suggestions - for improvement. -] - -The following steps should be taken each time a new release of linux-wlan -is ready for distribution: - -0) Make sure the current code builds, loads, associates, and ftps - cleanly on all 3 AVS lab build boxes. -1) Assign an W.X.Y-preZ version number. -2) Update the version number in config.in. -3) Tag the files. -4) Build the tarball. (Bonehead! double check next time that the tarball - and config.in version number match, eh?) -5) Release to ftp. -6) Announce on linux-wlan-annouce as a feature frozen 'pre' release. -7) Announce on freshmeat (Pavel? ;-) -8) Allow at least 24 hours for bug reports and (hopefully) bugfix patches. -9a) After 24 hour period, if bugfix patches and/or local fixes to bug - reports are present, apply patches and GOTO step 0. -9b) If no show-stopper bug-reports and/or patches are received during the - 'pre' release period GOTO step 10. -10) Make sure the current code builds, loads, associates, and ftps - cleanly on all 3 AVS lab build boxes. -11) Assign an W.X.Y version number. -12) Update the version number in config.in. -13) Tag the files. -14) Build the tarball. (Bonehead! double check next time that the tarball - and config.in version number match, eh?) -15) Release to ftp. -16) Announce on linux-wlan-annouce as a final W.X.Y release. -17) Announce on freshmeat. - |