Community
Participate
Working Groups
Since GIT garbage collects orphan commits, it is very important to tag releases so that merging accidents cannot orphan and so corrupt the release histories.
No idea about you mention of GIT behaviour. Anyway... There is an already created R3_1_1 tag for Indigio SR1. Concerning milestones.... I've only found a couple of pattern for milestones which I really dislike: M2_13 M6_12 Do you have any preference ? Some alternatives: - 4_0_M3 - Juno_M3 - S4_0_M3 Cheers, Adolfo.
(In reply to comment #1) > No idea about you mention of GIT behaviour. > > Anyway... There is an already created R3_1_1 tag for Indigio SR1. I can't see it. May be you need to PUSH. > Do you have any preference ? Some alternatives: > > - 4_0_M3 > - Juno_M3 > - S4_0_M3 I was going to continue R3_1 etc, but with plugins diverging the major version number is meaningless, so I prefer Juno_M3, Juno_RC1, Juno_SR2_RC3
Ed, As you said the tags were created in my local repository, but they had not been pushed. I have just pushed the following tags: R3_1 R3_1_1 Juno_M4_Core Juno_m4_Tools P.S: I think we could keep the RX_X convention for the final release. Resolving as fixed.
CLOSED after a year in the RESOLVED state.
