Convention for platform branches

[Sanchit Bahal]

I feel we need a naming convention for the ‘dev’ and the ‘release’ branches in the platform.

For example,

·        As a developer I may want to have a working branch with some name, say ‘spike_foobar’.

·        0.9 release of the platform might need a patch for which we would need to branch it out.

 

If we have a convention, it would be easier to differentiate the two. Any suggestions?

Also, the current list of branches itself has become quite big – there are 25 remote branches right now. Any thoughts on how this can be managed better?

 

Thanks,

Sanchit Bahal

Mobile: +91 9980141983

 

[Rob LaRubbio]

My preference would be to have a process for deleting branches, so the set of live branches are those that are under active development or were recently developed.  So we standardize on the release branch names and all other branches are free form.

-Rob