Out of curiosity, is there a reason for distributing the release on repository.a.o vs. dist.a.o?
In my experience repository.a.o has traditionally been used for maven artifacts, and dist.a.o has been for release artifacts (source archives and convenience binaries). I'd be happy to help with documenting the process. I ask because this might come up during an IPMC release vote. -Taylor > On Jun 1, 2016, at 9:46 PM, Davor Bonaci <da...@google.com.INVALID> wrote: > > Hi everyone! > We've started the release process for our first release, 0.1.0-incubating. > > To recap previous discussions, we don't have particular functional goals > for this release. Instead, we'd like to make available what's currently in > the repository, as well as work through the release process. > > With this in mind, we've: > * branched off the release branch [1] at master's commit 8485272, > * updated master to prepare for the second release, 0.2.0-incubating, > * built the first release candidate, RC1, and deployed it to a staging > repository [2]. > > We are not ready to start a vote just yet -- we've already identified a few > issues worth fixing. That said, I'd like to invite everybody to take a peek > and comment. I'm hoping we can address as many issues as possible before we > start the voting process. > > Please let us know if you see any issues. > > Thanks, > Davor > > [1] https://github.com/apache/incubator-beam/tree/release-0.1.0-incubating > [2] https://repository.apache.org/content/repositories/orgapachebeam-1000/
