X-Git-Url: http://www.privoxy.org/gitweb/?a=blobdiff_plain;f=doc%2Fwebserver%2Fdeveloper-manual%2Fnewrelease.html;h=4fd3b028036eebc76f39ff2755f970e92e8c7f81;hb=2c8c7bc03545ae4a2da7152b79d957cd0f9ff6bd;hp=069d37a44fb91d1b7b440efbd41b612744e7e373;hpb=743baf6ac2c438f9fc931d5910beec06fd61dd63;p=privoxy.git diff --git a/doc/webserver/developer-manual/newrelease.html b/doc/webserver/developer-manual/newrelease.html index 069d37a4..4fd3b028 100644 --- a/doc/webserver/developer-manual/newrelease.html +++ b/doc/webserver/developer-manual/newrelease.html @@ -652,7 +652,27 @@ Edit Release, instead of Add Release.

-

6.5. After the Release

+

6.5. Updating the RSS feed

+

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.

+
+
+

6.6. After the Release

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