incubator-blur-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Aaron McCurry <amccu...@gmail.com>
Subject Re: Getting master up to date
Date Fri, 27 Jun 2014 17:07:57 GMT
On Fri, Jun 27, 2014 at 10:14 AM, Garrett Barton <garrett.barton@gmail.com>
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 <amccurry@gmail.com> 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
> >
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message