README.release 2.54 KB
Newer Older
1 2 3 4

Things to do in preparation for a release:

- Modify faqstatic.ent to adjust the name of &release;, &releasename;,
5
  and &testingreleasename;
6 7 8 9 10 11 12 13
  
- Adjust the package numbers of faqstatic.ent:

  developers  --> calculated based on the number of GPG keys in the
    	          keyring, check www.debian.org/devel/people for
	          a complete list and remove the groups. The following
		  perl snippet  might be of use:

14 15 16
  $ lynx -source  http://www.debian.org/devel/people >/tmp/people 
  $ cat /tmp/people |
    perl -ne  'if ( /^\<dt\>/ && /\<strong\>(.*?)\<\/strong\>/) \
17 18 19
               { $name=$1; $name=~ s/\<.*?\>//g; print $name."\n"; }' |
    wc -l
  
20 21 22
  and substract 140 (the current number of group maintainers) from the
  count (look for DDs whose contact e-mail is Alioth since these
  tend to be team addresses)
23 24

  For packages:
25 26
  ( the count-release.sh script should do this automatically if
    properly adjusted )
27 28 29 30 31 32 33 34 35 36 37 38 39 40

  [ First calculate the number of packages in the distribution 
  (main+contrib+non-free): ]
   $ total=`grep-available -s Package -F section -r ".*" |wc -l`
  [ Then contrib and non-free ]
   $ nonfree=`grep-available -s Package -F section -r "non-free/.*" |wc -l`
   $ contrib=`grep-available -s Package -F section -r "contrib/.*" |wc -l`
 
  contrib-nonfree-pkgs   --> $(($nonfree+$contrib))
  main-pkgs   --> $(($total-$nonfree-$contrib))
  all-pkgs    --> $(($total-$nonfree))

  Note: The grep-available runs should be done in a &release; system
  of course or providing it a Packages file from
41 42 43
  /debian/dists/$RELEASE/main/binary-$ARCH/Packages
  /debian/dists/$RELEASE/contrib/binary-$ARCH/Packages
  /debian/dists/$RELEASE/non-free/binary-$ARCH/Packages
44 45 46 47

  The biggest $ARCH should be used here (typically, i386) since the numbers
  will vary from architecture to architecture.

48 49
- Review the number of architectures release. Check the Release Notes at:
  https://www.debian.org/releases/stable/
50

51
- Review the "oldcodenames" section in ftparchive.sgml to point to the
52
  oldreleasename and make sure that the "sourceforcodenames" section
53
  contains &releasename; and the next release (testing)
54 55 56 57 58 59

- Review the contents of nexttime.sgml. There is not always discussion on
  debian-devel of wanted features for the next release so spark the
  discussion if needed be to get a list of things that _might_ end up
  in the next release. Use the Release Goals set by release managers
  if there are any.
60 61

  More information for Release Goals here: https://wiki.debian.org/ReleaseGoals/
62 63
  
-- Javier Fernandez-Sanguino <jfs@debian.org>
64
Sun, 26 Apr 2015 17:04:07 +0200
65