Thanks for all of your responses. I'd just like to summarize for my own benefit:
1. Matt/James are taking the task of setting up our ability to deploy to repository.apache.org - we look forward to hearing when that will be ready. 2. We deploy both full releases and SNAPSHOTs to this repository. When we deploy to this repository, such deployments are automatically mirrored to central. SNAPSHOTs are not mirrored anywhere and those wishing to experiment with them must get them from repository.apache.org. 3. We should never promote SNAPSHOT releases anywhere except the dev mailing list. 4. We are free to publish SNAPSHOTs while under incubator. 5. I think we understand the process of "release" at this point, but for completeness of all that was said, a "release" is determined by vote via the PMC. A "release" is meant to be public and promoted to users. On Tue, Feb 10, 2015 at 11:31 PM, David Nalley <[email protected]> wrote: > On Tue, Feb 10, 2015 at 11:11 AM, Stephen Mallette <[email protected]> > wrote: > > Mentors, > > > > We've always deployed SNAPSHOT releases to Sonatype: > > > > https://oss.sonatype.org/content/repositories/snapshots/com/tinkerpop/ > > > > Based on that, I have couple of questions: > > > > 1. Will we still deploy SNAPSHOT releases to Sonatype under Apache? I did > > find this page[1] - do we simply follow those instructions? > > 2. While under incubator, are we allowed to publish SNAPSHOT releases? > > > > Apache projects publish via our own Nexus instance. > Sonatype mirrors our 'released versions' (something that has been > officially released) but they do not mirror SNAPSHOTS. > > Apache projects are prohibited from promoting to their users > SNAPSHOTs, but can promote them on their dev lists, and in other > places that the developers (but not users) of their project will see. > > Just a terminology thing, but SNAPSHOT and release are two different > things here. Releases are something that your project's PMC has > vetted, voted on, and approved for release. SNAPSHOTs (here) are > artifacts that are intended to only be seen by the developers of the > project, or perhaps users who want to test what is going to be the > next release. Some projects vote on things like alpha and beta > releases, and then publish those with alpha and beta titles to set > expectations for users but also allow them to widely promote the > release. > > --David > > > --David >
