OK, locally I can do whatever. But how am I supposed to get my work up to remote and master? Merge locally and then push?
10+ years with CM in my organisation have shown us that branched work is best integrated into the main (master) branch by some coordinating CM role. But Drools isn't being developed according to some standard Development Life Cycle. -W On 3 January 2011 14:38, ge0ffrey <ge0ffrey.s...@gmail.com> wrote: > > Imo, topic branches should be local > or remote on a fork. > i dont think we should litter reference with remote topic branches. > it should only have release branches. > look at hibernate on github. > -- > View this message in context: > http://drools-java-rules-engine.46999.n3.nabble.com/git-branches-origin-username-tp2180410p2184778.html > Sent from the Drools - Dev mailing list archive at Nabble.com. > _______________________________________________ > rules-dev mailing list > rules-dev@lists.jboss.org > https://lists.jboss.org/mailman/listinfo/rules-dev >
_______________________________________________ rules-dev mailing list rules-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/rules-dev
