Sounds good to me.
On Fri, Jun 27, 2014 at 1:07 PM, Aaron McCurry <[email protected]> wrote: > On Fri, Jun 27, 2014 at 10:14 AM, Garrett Barton <[email protected] > > > wrote: > > > This came up with some folks recently looking to use blur and confused on > > what branch is the best. Either we do away with master and work in > release > > versions (removing anything not 0.1x or 0.2x), or we cut a branch for > every > > version release off master. Either works. It sounds like you will do the > > later if your going to make master the most current, this correct? > > > > I think that as we cut a release we branch+tag. Thoughts? > > Aaron > > > > > > ~Garrett > > > > > > On Fri, Jun 27, 2014 at 9:59 AM, Aaron McCurry <[email protected]> > wrote: > > > > > Since we have been developing only on apache-blur-0.2 branch for a long > > > time I consider this to be the master branch. However the actual > master > > > does not reflect this and I would like to resolve this issue. > > > > > > So I would basically like to make the apache-blur-0.2 the master by > > > following the first answer on the question. > > > > > > > > > > > > http://stackoverflow.com/questions/2763006/change-the-current-branch-to-master-in-git > > > > > > Does anyone have an issues with this? > > > > > > Aaron > > > > > >
