Simplify HOWTO_RELEASE document

[strk]

It's too complicated.

• Asks to checkout the tag for no reason (make_dist.sh would do that)
• Misses to ask testing the tarball before upload
• Requests to do something which should be automated (#2735 + extension stuff)

[strk]

SVN checkout step removed and testing of tarball step added as of r12556 in 2.0 branch, r12558 in 2.1 branch, r12560 in trunk.

[strk]

r12562 in trunk, r12563 in branch drop the download link step Only thing missing is the upgradable_versions step. It might be simpler to delegate it to another ticket.

Regina, ideas about automation of that ?

[robe]

I like your changes, but not sure following what you are saying with the rest.

I think we can take out PlanetPostGIS. That gets updated automatically when you post to the website since PostGIS dev blog is part of PlanetPostGIS and PlanetOSGEO feed. Technically it's part of PlanetPostgreSQL as well but we have loose ends to take care of there.

[strk]

I mean this snippet: ​https://github.com/postgis/postgis/blob/2.1.3/HOWTO_RELEASE#L49-L54

[strk]

Another part: it turns out we need to also upload to osgeo.org the PDF and the HTML manual, not clearly stated in the HOWTO_RELEASE file

[strk]

PlanetPostgis announce removed with r12573 in 2.1 branch and r12575 in trunk. Was not present in 2.0. The announcement there happens automatically from editing the PieCrust news file

[strk]

I understand this part of the release procedure still needs to be simplified somewhat: ​https://github.com/postgis/postgis/blob/2.1.3/HOWTO_RELEASE#L49-L54

Postponing to the virtual "never" milestone.

[robe]

Milestone renamed