Thank Josh for the house cleaning, I like to have clear branches and like
Joe said more feature branches to experiment, try, discuss, review, etc..
On Wed, Oct 22, 2014 at 5:55 PM, Tim Kim timki...@gmail.com wrote:
Yep, delete em.
On 22 October 2014 12:50, Andrew Grieve agri...@chromium.org
Agreed. We should delete feature branches once they're merged in. That
said, we should have a LOT more feature branches.
On Wed, Oct 22, 2014 at 9:52 AM, Josh Soref jso...@blackberry.com wrote:
There are a number of branches in cordova-js.
I think there should be two kinds of branches:
1.
+1, merged feature branches should be deleted
pinging the relevant committers so they can come rescue anything they want
to save would be prudent for the 4. stale/abandoned branches.
On Wed, Oct 22, 2014 at 10:14 AM, Joe Bowser bows...@gmail.com wrote:
Agreed. We should delete feature branches
I just added a step in the committer workflow in coho/docs.
http://git-wip-us.apache.org/repos/asf/cordova-coho/commit/facce79c
On Oct 22, 2014, at 1:14 PM, Joe Bowser bows...@gmail.com wrote:
Agreed. We should delete feature branches once they're merged in. That
said, we should have a LOT
Yep, delete em.
On 22 October 2014 12:50, Andrew Grieve agri...@chromium.org wrote:
On Wed, Oct 22, 2014 at 12:52 PM, Josh Soref jso...@blackberry.com
wrote:
There are a number of branches in cordova-js.
I think there should be two kinds of branches:
1. Release branches (or tags that
