I'm not sure what to do here. INFRA just changed the Git behavior so it is no longer possible to delete branches. I generally don't like to have failed branches in a release history (otherwise you get a release branch with all these maven forward/backwards commits). As such, I would overwrite candidate branches historically (dropping the failed release commits).
The commit is here right now: https://github.com/jacques-n/drill/tree/drill-1.3.0-rc0 The parent of 4822068a006aeb251b686d2b51871573c4337e60 is 3dedc158f3af8ec8320a9cd336b2798b09cc9a8d (the tip of master) -- Jacques Nadeau CTO and Co-Founder, Dremio On Thu, Nov 5, 2015 at 1:01 PM, Aditya <[email protected]> wrote: > I am having trouble determining the git commit this release is based on as > I could not find the > id (4822068a006aeb251b686d2b51871573c4337e60) captured in the > git.properties bundled in the > tarballs in the Drill Git repository. > > Most likely the last commit is only in your local branch and since > git.properties captures only the > last commit, it is impossible to find the parent commit. > > Would it make sense to push the release branch? > > aditya... > > On Wed, Nov 4, 2015 at 11:08 PM, Jacques Nadeau <[email protected]> > wrote: > > > Hey Everybody, > > > > I'm happy to propose a new release of Apache Drill, version 1.3.0. This > is > > the first release candidate (rc0). It covers a total of ~50 closed JIRAs > > [1]. > > > > The tarball artifacts are hosted at [2] and the maven artifacts are > hosted > > at [3]. > > > > The vote will be open for 72 hours ending at 11PM Pacific, November 7, > > 2015. > > > > [ ] +1 > > [ ] +0 > > [ ] -1 > > > > thanks, > > Jacques > > > > [1] > > > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12313820&version=12332946 > > [2] http://people.apache.org/~jacques/apache-drill-1.3.0.rc0/ > > [3] > > https://repository.apache.org/content/repositories/orgapachedrill-1013/ > > >
