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.
Partway through.
Now the its I have never done before hit me ...
anything in particular to look for in the diff?
how (and where? my machine or squid-cache.org server?) do I do the
verification and signing?
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
you mean a cvs checkout of www2 branch in website repository? or is
there a 'co' program?
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.
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.
