Em Ter, 2004-01-06 �s 12:54, Joachim Breitner escreveu: > So the first person do change something after a release has his name in > the changelog entry. Now should changes by other persons before the next > release > a) marked and named, to trace back and avoid false accusations > b) not marked for better readablity and since the changelog is for the > user (we have the CVS). > I'd vote for b)
I'd vote for b also, that means: "debchange -i" once per release and "debchange -a" the rest of the time. > > For each debian revision. and > > yes, the debian_version tag should only be made when there is a release > > to be done. > > > > In the case above (nomeata quote), there is no need to move the tag > > debian_version_0_71-1, just create a new tag debian_version_0_71_2. > Thats a contradiction (as far as I see it). > The first debian release is tagged debian_version_0_71-1. Using > cvs-update, all files are already tagged debian_version_0_71-1, so when > we change stuff before we actually release the new version (which is > very likely), we have to re-tag it again to debian_version_0_71-1. Ok, maybe I wasn't clear... The proccess is exactly what you described. I mean the new tag after the release of that version. daniel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
