Sure, I will change the branch to sentry-2.0 Thanks, Kalyan
-Kalyan On Mon, Nov 27, 2017 at 10:54 AM, Sergio Pena <sergio.p...@cloudera.com> wrote: > That's old Kalyan. Why do you propose bringing back the old approach? The > new approach is used by other Apache components where bugfix releases are > only tags. This reduces the release process and steps of bugfix releases. > > On Mon, Nov 27, 2017 at 10:36 AM, Kalyan Kumar Kalvagadda < > kkal...@cloudera.com> wrote: > > > Sergio, > > > > If you look at all the previous branches they are followed convention > > sentry-major.minor.patch. I tried to be in-line with them. > > > > -Kalyan > > > > On Mon, Nov 27, 2017 at 9:35 AM, Sergio Pena <sergio.p...@cloudera.com> > > wrote: > > > > > Great, thanks Kalyan. > > > > > > Btw, the branch should be named branch-2.0 as the Wiki suggests (git > > > checkout -b branch-1.8). It is better to name a branch this way so we > can > > > commit bugfixes on it for future 2.0.x bugfix releases. > > > > > > On Mon, Nov 27, 2017 at 8:19 AM, Kalyan Kumar Kalvagadda < > > > kkal...@cloudera.com> wrote: > > > > > > > I've just created new release branch for upcoming 2.0.0 release. > Please > > > > continue committing to master branch as usual. > > > > I'll cherry-pick commits to branch-2.0.0 on need basis. > > > > > > > > -Kalyan > > > > > > > > > >
