Task #2794 (closed)

Opened 3 years ago

Last modified 3 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 Keywords: n.a.
Cc: developer, jburel, cxallan, jamoore Remaining Time: 0.0d
Sprint: 2010-09-09 (16) Resources: n.a.
References: n.a. Referenced By: n.a.

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

comment:1 Changed 3 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 3 years ago by jburel

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

comment:3 Changed 3 years ago by jburel

  • Owner set to jburel
  • Status changed from new to assigned

comment:4 Changed 3 years ago by jmoore

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

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

comment:5 Changed 3 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.

1.3.2-PRO © 2008-2010 agile42 all rights reserved (this page was served in: 2.328508 sec.)

© 2000-2013 University of Dundee & Open Microscopy Environment. Creative Commons Attribution 3.0 Unported License
OME source code is available under the GNU General public license or through commercial license from Glencoe Software

We're Hiring!