#472 closed request (fixed)
extend make release target
Reported by: | Peter | Owned by: | Peter |
---|---|---|---|
Priority: | major | Milestone: | yat 0.5 |
Component: | build | Version: | trunk |
Keywords: | Cc: |
Description
There are a couple of flaws in the release procedure.
The most important is that make svn-clean
is dangerous. I've had a couple of accidents with severe data loss. Obviously one might lose subdirs not under svn control. A more tricky case is that one might lose svndigest cache (which is pretty annoying too although it can be re-created). Therefore, I suggest that we remove svn-clean from the ReleaseProcedure. Instead one should checkout a fresh svn wc (or perhaps export) and perform the test on that pristine checkout. In principle something like this:
svn export <url.my> tmp_wc cd tmp_wc ./bootstrap mkdir build_ cd build_ ../configure make distcheck
The fact that I can write the commands, kind of suggests that we should have this as a script instead.
Moreover, I think that 5) and 9) should come together and they should probably come before 7) because the milestone that might be created in 9) is linked to when updating links in 7). To make it easy for RM I'd prefer to avoid jumping between svn and trac. So I suggest the following
After dist and tag are created (4 and 5), prepare the stable-branch (7), then update versions and milestones in trac (5 and 9 respectively), followed by updating DownloadPage, and finish with a merge.
Also, there is no need to generate html. For patch release that point is outdated since we no longer creates docs against tags but against the branch. Also for the minor release it is not needed. Instead when creating the branch, RM should email the documentation manager and he will change to build docs against the new branch, perhaps against both branches for a transition period (until the new branch has been released).
Change History (4)
comment:1 Changed 13 years ago by
comment:2 Changed 13 years ago by
Status: | new → assigned |
---|
comment:3 Changed 13 years ago by
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
svn export
supports exporting from a wc e.g. through:This is preferable rather than export from repository. Though we should check that there is no difference between wc and repo.