I think everything is as intended? The head of ASF and Gerrit right now are at the same commit (8b4b9d4). I was using Gerrit as a staging area, but once I got everything in good shape, I pushed it to ASF for the release vote.
The maven release plugin requires us to push directly to Gerrit's head, but that's been a known quirk since we first tried releasing Hyracks after starting with Gerrit. @Abdullah, you can just go ahead and depend on Hyracks 0.2.17-SNAPSHOT in your branch. We shouldn't bump the version in master, because we still intend to release AsterixDB after Hyracks, so it needs to depend on 0.2.16-incubating (whenever it exists). - Ian On Wed, Sep 2, 2015 at 12:53 AM, Chris Hillery <[email protected]> wrote: > Looks like those maven-release-plugin commits got pushed directly to > Apache, bypassing Gerrit. That's... unfortunate, I think, but probably > salvageable. Ian? > > Ceej > aka Chris Hillery > > On Wed, Sep 2, 2015 at 3:48 AM, abdullah alamoudi <[email protected]> > wrote: > >> What is interesting here is that while Hyracks in Github repository: >> https://github.com/apache/incubator-asterixdb-hyracks has a version of >> 0.2.17-SNAPSHOT, the last merged change in Gerrit still shows the version >> as 0.2.16-SNAPSHOT. >> >> So the question is: How did that happen? >> >> On Wed, Sep 2, 2015 at 12:55 PM, abdullah alamoudi <[email protected]> >> wrote: >> >> > Hi, >> > Did we pump hyracks version to 0.2.17 on Gerrit without changing the >> > reference in asterixdb pom file? >> > >> > I believe that my change for the filesystem based feed adapter is unable >> > to build on Gerrit because of this. >> > >> > Cheers, >> > Amoudi, Abdullah. >> > >> >> >> >> -- >> Amoudi, Abdullah. >>
