Hey Stephen, Yes this runs afoul of good practice in Maven where a given version shouldn't be re-used. As far as I understand though, it is required by the way the Apache release process works.
The artifacts and repository content that get voted on need to exactly match the final release. So we can't hold a vote on a version of the code where everything says "-rcx", then we go back and change the source code and do a second push to maven with code that doesn't have an "-rcx" suffix. This would effectively change the code that is being released. I was thinking as a work around that maybe we could publish a second set of staging artifacts that are versioned with -rcX for people to test against. I think as long as we make it clear that these are not the "official artifacts" being voted on it might be okay. I'm not totally sure if this is allowed though. - Patrick On Tue, Jan 28, 2014 at 9:01 AM, Stephen Haberman <stephen.haber...@gmail.com> wrote: > Hi Patrick, > >> The staging repository for this release can be found at: >> https://repository.apache.org/content/repositories/orgapachespark-1006/ > > I was going to import this rc5 release into our internal Maven repo to > try it out, but noticed that the version doesn't have "rc5" in it. > > This means that, if there is an rc6, I'll have to re-import over the same > artifacts, which is generally not a good thing given Maven assumes artifacts > never change. > > Is this restriction required by the blessing process, or would it be > possible to sneak rc5 into the pre-final version number? > > For now, I'll just build a local version, at the same commit, but with > the as 0.9.0-incubating-rc5. > > Apologies if this was discussed before and I just missed it. > > - Stephen >
