Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 363266

Summary:	[releng] Where are the GIT tags for 3.1.1 and M-builds?
Product:	[Modeling] OCL	Reporter:	Ed Willink <ed>
Component:	Core	Assignee:	OCL Inbox <mdt-ocl-inbox>
Status:	CLOSED FIXED	QA Contact:
Severity:	major
Priority:	P3
Version:	3.2.0
Target Milestone:	---
Hardware:	PC
OS:	Windows Vista
Whiteboard:

Description Ed Willink

2011-11-09 04:14:20 EST

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.

Comment 1 Adolfo Sanchez-Barbudo Herrera

2011-11-09 05:15:51 EST

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.

Comment 2 Ed Willink

2011-11-09 11:52:01 EST

(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

Comment 3 Adolfo Sanchez-Barbudo Herrera

2011-12-15 06:28:10 EST

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.

Comment 4 Ed Willink

2013-05-20 11:35:21 EDT

CLOSED after a year in the RESOLVED state.