Amos Jeffries wrote:
Henrik Nordstrom wrote:
On Thu, 2008-02-28 at 01:04 +1300, Amos Jeffries wrote:
Just a few issues remaining before 3.0.STABLE-2.

  * patch 11467 back-porting.

cd English
ls ERR_* >../list

  * Close more bugs?
       http://www.squid-cache.org/bugs/show_bug.cgi?id=2127

Is closed and verified by the reporter.

       http://www.squid-cache.org/bugs/show_bug.cgi?id=2124

Done.

     why is this not 2.6??
       http://www.squid-cache.org/bugs/show_bug.cgi?id=2138

Don't know.

  * CVS branching? checkpoint?.
       Will need another How-To here I think Henrik.t

update releasenotes and changelog.

login on squid/cache.org and

- get an up to date checkout of the tree
  cvs up -d -P
- make sure the version in configure.in is correct
- ./bootstrap.sh
- cvs commit
- cvs tag SQUID_3_0_STABLE2
- ./mkrelease.sh squid-3.0.STABLE2 /server/httpd/htdocs/squid-cache.org/Versions/v3/3.0/
  (i think, verify the path)
this should give you a suitable tarball in the website.

download that, and the previous release and signature as well.

verify the signature of the previous release

make a diff between the two, and audit that diff to verify that the
changes looks right.

sign the new release and diff.

upload the diff and signatures to the 3.0 folder on the web server.

go to the 3.0 web folder

co -l index.tmpl

edit index.tmpl, moving the previous release down to "older stable
releases" and the new as current stable release.

./make.sh

verify that it got published right.


Thanks to Henrik I'm now up to here.

Just two problems preventing completion.

1) I don't have write access to the FTP area to copy the files in.
   I think its /server/ftp/pub/squid-3/STABLE/ anyway.
   (The STABLE1 signature files and diff appear to be missing too)

2) my PGP key probably needs to be added to the keyring at
   http://www.squid-cache.org/pgp.asc before the announce.


copy the tarballs, diff, release notes and signatures to the ftp area.

send announce


Amos
--
Please use Squid 2.6STABLE17+ or 3.0STABLE1+
There are serious security advisories out on all earlier releases.

Reply via email to