X-Git-Url: http://www.privoxy.org/gitweb/?a=blobdiff_plain;ds=sidebyside;f=doc%2Fwebserver%2Fdeveloper-manual%2Fnewrelease.html;h=fd3bed4e410aa5b7126ae11fd82b1f511a1218ee;hb=HEAD;hp=069d37a44fb91d1b7b440efbd41b612744e7e373;hpb=f496cc8ffc3f43f6b154a1f4261a38a9b21f7c16;p=privoxy.git diff --git a/doc/webserver/developer-manual/newrelease.html b/doc/webserver/developer-manual/newrelease.html index 069d37a4..f973801d 100644 --- a/doc/webserver/developer-manual/newrelease.html +++ b/doc/webserver/developer-manual/newrelease.html @@ -492,7 +492,7 @@
- dch -v 3.0.34-1+ dch -v 3.0.35-1 |
- lintian -iI ../build-area/privoxy_3.0.34-1_amd64.changes+ lintian -iI ../build-area/privoxy_3.0.35-1_amd64.changes |
sudo cowbuilder --build --basepath /var/cache/pbuilder/base.cow ../build-area/privoxy_3.0.34-1.dsc+ "PROGRAMLISTING"> sudo cowbuilder --build --basepath /var/cache/pbuilder/base.cow ../build-area/privoxy_3.0.35-1.dsc
autopkgtest /var/cache/pbuilder/result/privoxy_3.0.34-1_amd64.changes -s -- schroot sid+ "PROGRAMLISTING"> autopkgtest /var/cache/pbuilder/result/privoxy_3.0.35-1_amd64.changes -s -- schroot sid
Or just push the changes to salsa.debian.org, where a CI pipeline is defined for the package, that builds and tests it.
If everything is okay, run cowbuilder with i386 and amd64 environments for current Debian stable release and - build privoxy_3.0.34-1_i386.deb and privoxy_3.0.34-1_amd64.deb. Then sign both files:
+ build privoxy_3.0.35-1_i386.deb and privoxy_3.0.35-1_amd64.deb. Then sign both files:
- gpg --detach-sign --armor privoxy_3.0.34-1_i386.deb - gpg --detach-sign --armor privoxy_3.0.34-1_amd64.deb+ gpg --detach-sign --armor privoxy_3.0.35-1_i386.deb + gpg --detach-sign --armor privoxy_3.0.35-1_amd64.deb |
Once the packages are uploaded to SourceForge they should be mirrored on the Privoxy websites (https://www.privoxy.org/ and http://l3tczdiiwoo63iwxty4lhs6p7eaxop5micbn7vbliydgv63x5zrrrfyd.onion/). This is usually done by + Fabian who uses a couple of shell functions for this that aren't documented or published yet.
+Once the packages are uploaded to the mirror the RSS feed has to be regenerated with a command like:
+
+ fk@t520 ~/git/privoxy $utils/create-package-feed.pl /tank/backups/sourceforge/frs/project/ijbswa/ doc/webserver/feeds/privoxy-releases.xm ++ |
+
The updated RSS feed then has to be uploaded to the SourceForge webserver and mirrored on the Privoxy websites + again. This, too, is usually done by Fabian with undocumented and unpublished shell functions.
+When all (or: most of the) packages have been uploaded and made available, send an email to the announce mailing list, Subject: "Announcing Privoxy X.Y.Z $CODE_STATUS". Be sure to include the