Context Navigation

Notice: In order to edit this ticket you need to be either: a Product Owner, The owner or the reporter of the ticket, or, in case of a Task not yet assigned, a team_member"

Task #2794 (closed)

Opened 9 years ago

Closed 9 years ago

Last modified 9 years ago

Decide on branching strategy for 4.2.1

Reported by:	jamoore	Owned by:	jburel
Priority:	blocker	Milestone:	OMERO-Beta4.2.1
Component:	Deployment	Version:	n.a.
Keywords:	n.a.	Cc:	developer, jburel, cxallan, jamoore
Resources:	n.a.	Referenced By:	n.a.
References:	n.a.	Remaining Time:	0.0d
Sprint:	2010-09-09 (16)

Description

Due to the current use of trunk for the delete work, we will either need to backport a significant number of commits to source:branches/Beta4.2 or decide to branch 4.2.1 off of trunk.

See discussion from Sep.2

References

Change History (5)

comment:1 Changed 9 years ago by jburel

Cc jmoore added

Following 07/09 meeting.

Evaluate side effects of changes, in trunk, not directly related to selected topics (VM, delete) e.g. EM
If no major side effects, create a 4.2.1 branch.

comment:2 Changed 9 years ago by jburel

Sprint changed from 2010-08-26 (15) to 2010-09-09 (16)

comment:3 Changed 9 years ago by jburel

Owner set to jburel
Status changed from new to assigned

comment:4 Changed 9 years ago by jmoore

Remaining Time changed from 1 to 0
Resolution set to fixed
Status changed from assigned to closed

Chosen strategy: replace 4.2 branch with trunk rather than backporting.

comment:5 Changed 9 years ago by jmoore

(In [8376]) Rolling back to 4.2.1-DEV (See #2794)

Note: See TracTickets for help on using tickets. You may also have a look at Agilo extensions to the ticket.

Download in other formats: