Git-Url: 
http://git.frugalware.org/gitweb/gitweb.cgi?p=frugalware-current.git;a=commitdiff;h=a0411e3e2f705635fb38f8fa71e1f1e535cf59b5

commit a0411e3e2f705635fb38f8fa71e1f1e535cf59b5
Author: Miklos Vajna <[EMAIL PROTECTED]>
Date:   Sat Sep 6 16:13:35 2008 +0200

docs/release-howto: next time it'd be better to write the upgrade howto before 
tagging the release

diff --git a/docs/release-howto.txt b/docs/release-howto.txt
index 76f18ee..7db9086 100644
--- a/docs/release-howto.txt
+++ b/docs/release-howto.txt
@@ -26,6 +26,8 @@ $ rsync -avP --delete-after frugalware-current/ 
frugalware-testing/
- run gensync to rebuild the fdbs
- generate isos and test if everything is ok
(ie. install from cd1-cd2 on i686, and start kde, or something)
+- check if the upgrade from 0.4->0.5 works or not, probably a simple -Syu is
+  not enough, then write a howto
- tag the release using git tag

== Creating the stable tree
@@ -53,7 +55,7 @@ STABLE = true

in the Makefile
- s/-current// in tools/mkpkglst
-- update VERSION in docs/Makefile
+- update VERSION in docs/Makefile, and rebuild the manual
- update `\.git/description`
- update kernel FrugalBuild to hardwire the kernel release (`\_F_kernel_rel`)
- update `/source/include/kernel-module.sh` (s/=/>=/) and rebuild the fdbs
@@ -71,8 +73,6 @@ STABLE = true
- generate isos, test _all_ of them (net,cd,dvd for each arch)
- create an usb stick installer tarball for each arch
- create an tftp boot image for each arch
-- check if the upgrade from 0.4->0.5 works or not, probably a simple -Syu is
-  not enough, then write a howto and rebuild the manual

== Announcement
_______________________________________________
Frugalware-git mailing list
[email protected]
http://frugalware.org/mailman/listinfo/frugalware-git

Reply via email to