Jump to content


Release Stream Parenting

release streams parent patch reparent

  • Please log in to reply
1 reply to this topic

#1 GodfatherofSoul

GodfatherofSoul

    Newbie

  • Members
  • Pip
  • 3 posts

Posted 14 November 2014 - 05:46 PM

This question is about parenting release versions from to their successors.  Is there a point at which you stop this chaining?  Is it something only done for patch versions or is the convention to chain all active branches?

e.g. If I have versions 1.0,1.1,1.2,1.3,2.0,2.1,2.2, 2.2.1, and 2.2.2  what I've seen suggests this:

1.0 -> 1.1 -> 1.2 -> 1.3 -> 2.0 -> 2.1 -> 2.2 -> 2.2.1 -> 2.2.2 -> mainline

But that seems like it could conceptually get pretty tall over time.  Should they all be stacked or would their be shorter chains?

1.0 -> mainline
1.1 -> mainline
1.2 -> mainline
1.3 -> mainline
2.0 -> mainline
2.1 -> mainline
2.2 -> 2.2.1-> 2.2.2 -> mainline

or possibly

1.0 -> 1.1 -> 1.2 -> 1.3 -> mainline
2.0 -> 2.1 -> 2.2 ->2.2.1 -> 2.2.2 -> mainline

#2 Krzysztof Nosek

Krzysztof Nosek

    Member

  • Members
  • PipPip
  • 21 posts

Posted 17 November 2014 - 08:11 AM

First of all, we've been removing older releases (by deleting their streams) to mark those which are no longer practically supported. Which means, there are no further actual or possible clients using this or any older release. We haven't hit a major revision yet though, so the question about the length of chains sounds very interesting to me. I think that if there's a major incompatibility between 1.3 and 2.0 you are not going to merge down fixes from 1.x to 2.x this way anyway - since in the general case this may not be even possible or safe - your proposition of cutting the chain of releases into two lines is very good.





Also tagged with one or more of these keywords: release, streams, parent, patch, reparent

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users