So.. we are ready for a release.. great :) 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, we don't want to make another release that is essentially the same, and it is weird in my opinion to have 0.96rc2 followed by a 0.97 release. to be short with rc then you have to make as much rc's until there are no more bugs, and then make another release that is only a namechange from rc to normal. With the .bugfix releases none of these problems exist, and computers will have an easier time to understand what version is newer.
2) are all binaries updated? 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. 4) I guess that's it..
signature.asc
Description: This is a digitally signed message part
_______________________________________________ Amsn-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/amsn-devel
