Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
Overview
| Artifact ID: | 87135bab600e5656ff61d11677698c2a29b37664a8e0b5866e2f817a5e609e5b |
|---|---|
| Page Name: | How to make a release |
| Date: | 2018-01-08 18:33:44 |
| Original User: | oehhar |
| Parent: | 9bf490dc7532f6cd28ced86e6e96f796ea51f21f9dd1f60b7ad66dcb9c08460e (diff) |
| Next | 945270a5ce771771557224269fa5264bde88166ba9f61c9d62e744eecff4ea05 |
Content
How to make a release
Here are the steps I do:
- Roll the version numbers to the new release version
- Tag the head with "Release_X.Y.Z" where X is the major version, Y is the minor version and Z is patch number (e.g. Release_2.4.0)
- Add a Tech-note with the release notes (see https://www.fossil-scm.org/xfer/doc/trunk/www/event.wiki for details)
- Add a line to the Downloads wiki page pointing to the release notes and the tar ball and zip file links for the node you tagged with the Release_.X.Y.Z tag. Edit the release numbers and the checkin uuids.
- Change wiki page "Web Services for Tcl (aka tclws)" to point to new documentation. (Change Release_x.y tag in reference).
- Post an announcement to c.l.t.
(info sent by Gerald 2018-01-08)