[Pulp-list] [devel] Is master going to be 2.6 or 3.0 (an API change question)?

Randy Barlow rbarlow at redhat.com
Wed Sep 24 14:17:56 UTC 2014


On 09/24/2014 09:51 AM, Brian Bouterse wrote:
> Even so, we should track the work for X and Y releases separately by creating a 2.6-dev branch and letting master be 3.0. There really isn't a downside except one additional merge, but I think it's worth it. The upside is we can always check in work when we need to, where we need to, and allow X and Y releases to mature until they are ready to be released. That seems worth the cost of one additional merge. What do you think?

My hesitation is due to us not being sure whether there will be a 2.6
release. I'd prefer not to create 2.6 branches if we aren't going to
make a 2.6 release (i.e., if 3.0 is next). I'd prefer to wait it out and
see what happens first.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: OpenPGP digital signature
URL: <http://listman.redhat.com/archives/pulp-list/attachments/20140924/073d0aee/attachment.sig>


More information about the Pulp-list mailing list