> 1) now we have to update the version in the amsn file.. what should it > become? More generally, what will this release be? > 0.96rc1 followed by rc2, then rc..., then 0.96 > or 0.96 followed by 0.96.1, etc > i would say the second, because if we don't have critical bugs, ...
I agree, I think the second, because that is what we have always done before. > 2) are all binaries updated? Why not? > 3) do we create a tag for this release in svn? (A tag and a branch are > the same in svn, technically) So does it have any benefits to create a > tag, when we already have a 0.96 branch, which we can check out by > revision number, if bugfixes later are done in this branch. Make a tag on the main branch? That is pointless because that isnt the 0.96, and we arent going to be integrating changes (accept for bugfixes if we plan to release a 0.96.1). So I think we don't need to tag it. _______________________________________________ Amsn-devel mailing list Amsn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amsn-devel
