Well, as you can see in the docs, "release" is a process of creating the artifacts for the community to test, review and the VOTE (that vote is starting should be announced to the Incubator PMC, i.e. general@ list) upon. Once successful vote here, a VOTE is also needed by the Incubator PMC.
Not until that vote is successful are allowed to "publish" the release to the general public, such as download page on website or Maven repositories. Hope that clarifies the workflow a bit... -- Niclas On Oct 1, 2009 8:16 PM, "Jonathan Costers" <[email protected]> wrote: I would definately NOT back out the POMs that were committed before. They are an excellent starting point for eventually publishing River artifacts to Maven repositories. Let's finish the discussion about the -dl JARs, but let's release first. If everyone agrees, I'll change the version number from 2.1.1 to 2.2.0 in the Ant build (when I get home tonight) and let Hudson pick it up. In about an hour after that we will have AR2 aka River 2.2.0. Getting AR2 out also means: - publishing the artifacts to the River web site - updating docs? - announcing it Thanks Jonathan 2009/10/1 Peter Firmstone <[email protected]> > By the sound of what Dennis is saying, it appears more to be a > classification issue rather than...
