Re: [p2-dev] integration vs. master branch

[Thomas Watson <tjwatson@xxxxxxxxxx>]

Developers wanting to work on a large new feature are free to develop them in a topic branch for ongoing development and review.  One downside to this is that it will not be included in the nightly builds until you merge the topic branch into master.

Also keep in mind that master must be kept integration build ready since an integration respin build may be requested one or two days after the normal Tuesday integration build.  Before we had an explicit opt-in model to participate in an integration respin build.  Now the content of master will be included in any respins.

Tom



Ian Bull ---10/18/2012 02:17:37 AM---Please see bug [1]. p2 is moving away from the integration / master branch approach.  That is, the i

From: Ian Bull <irbull@xxxxxxxxxxxxxxxxx>
To: P2 developer discussions <p2-dev@xxxxxxxxxxx>, Pascal Rapicault <pascal@xxxxxxxxxxxxx>,
Date: 10/18/2012 02:17 AM
Subject: [p2-dev] integration vs. master branch
Sent by: p2-dev-bounces@xxxxxxxxxxx

---

Please see bug [1]. p2 is moving away from the integration / master branch approach.  That is, the integration builds will now build from 'master'.  If we suddenly get a flurry of activity, or someone wants to spend some time working on a large new feature, we can easily return to this mode of operation.

[1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=391789

cheers,
Ian

-- 
R. Ian Bull | EclipseSource Victoria | +1 250 477 7484
http://eclipsesource.com | http://twitter.com/eclipsesource_______________________________________________
p2-dev mailing list
p2-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/p2-dev