Hi Lewis, I create Feature Branches for virtually everything when using shared GitHub and BitBucket repositories, because the Peer Review mechanism is so easy to support. We could look into the Apache Peer Review mechanism ( reviews.apache.org) but it may create an extra hassle if the process is not as smooth as that.
For now, if you want Peer Review create a branch (based on the Jira issue identifier) and comment on the relevant Jira issue to indicate that the code is ready for review. Otherwise there is no need to create branches if you don't want a Peer Review given the extra overhead for the submitter. However, having said that, I am likely to create branches for most issues, based on the Jira issue identifier, as I like to review my own commits that way and it is easy to do that using GitHub once I push the branch there, even if I can't use Pull Requests. Peter On 22 May 2013 06:01, Lewis John Mcgibbney <[email protected]>wrote: > Hi All, > I understand that there are only a few of us developing ANY23 now. > None-the-less it would be nice to establish some agreement about branching. > Are we going to create a branch for every issue? Or just complex ones? > I've created two branches, bu not sure that they were really that > necessary... that being said, I really don't know as we've not come to > agreement on anything. > Thanks > Lewis > > > -- > *Lewis* >
