Hello all, I have created SENTRY-1828 <https://issues.apache.org/jira/browse/SENTRY-1828> to rename version in sentry-ha-redesign branch to 2.0.0-SNAPSHOT. I will submit a patch for the same later today.
-Kalyan On Mon, Jun 26, 2017 at 10:32 AM, Kalyan Kumar Kalvagadda < [email protected]> wrote: > Sergio has a valid point. It is ideal to rename sentry-ha-redesign to > master and create 2.0 branch when it is ready for release. > > -Kalyan > > On Mon, Jun 26, 2017 at 9:45 AM, Sergio Pena <[email protected]> > wrote: > >> I agree that we should change the version number, but I kind of disagree >> on >> renaming the branch to a version that is not released yet. I've seen in >> other components including Sentry that a branch-X is created once is >> released. If we do rename sentry-ha-redesign to branch-2, are we going to >> rename it to master later? or we would have branch-2 and master with the >> same commits? >> >> >> On Fri, Jun 23, 2017 at 3:17 AM, Colm O hEigeartaigh <[email protected] >> > >> wrote: >> >> > +1 to all three. >> > >> > Colm. >> > >> > On Thu, Jun 22, 2017 at 7:20 PM, Alexander Kolbasov <[email protected] >> > >> > wrote: >> > >> > > I would suggest renaming Sentry HA to 2.0.0-SNAPSHOT >> > > >> > > I would also suggest to rename sentry-ha-redesign branch to 2.0 >> branch. >> > > >> > > We also should start thinking about opening 1.8 branch and moving >> current >> > > sentry HA to master. >> > > >> > > - Alex >> > > >> > > On Thu, Jun 22, 2017 at 3:06 AM, Colm O hEigeartaigh < >> > [email protected]> >> > > wrote: >> > > >> > >> Hi all, >> > >> >> > >> We should change the version of the ha branch to avoid conflict with >> the >> > >> master branch. Both are currently 1.8.0-SNAPSHOT. >> > >> >> > >> Colm. >> > >> >> > >> >> > >> -- >> > >> Colm O hEigeartaigh >> > >> >> > >> Talend Community Coder >> > >> http://coders.talend.com >> > >> >> > > >> > > >> > >> > >> > -- >> > Colm O hEigeartaigh >> > >> > Talend Community Coder >> > http://coders.talend.com >> > >> > >
