Shouldn't we make a tag of branches/0_96 now (called tags/0_96_1) ? I think so, because if we commit to 0_96 after the release, we cannot know what exactly was 0.96.1 in the repository anymore. And I think that is what Sander meant. And, iirc, it doesn't consume much repository space, as it is stored quite clever.
After reviewing and committing changes between the branch and trunk, the diff between branch and trunk is almost empty now. Why did we create the branches/0_96 in the first place? Was the idea, stop implementing new features so we can release? (that would be good I think) Or am I missing something? Jonne. > > 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
