@Justin We(Apache Camel) use the nexus stage repo for release candidate verification, as the end user may use maven to download the artifact jars instead of just use the zip artifacts.
As the Apache release distribution directory are synced which other mirrors site, it could confuse the user when we just replace the new released artifacts with the old one. @yukon Please take a look at the release guide[1], you may need to do some setup on your computer first to upload the artifacts to the nexus. For my Camel release experience, it could be better if you use AWS box instead of your own computer for better network connection (which is not blocked by the Great Fire Wall) [1]http://camel.apache.org/release-guide.html Willem Jiang Blog: http://willemjiang.blogspot.com (English) http://jnn.iteye.com (Chinese) Twitter: willemjiang Weibo: 姜宁willem On Thu, Feb 2, 2017 at 8:15 PM, Justin Mclean <[email protected]> wrote: > Hi, > > > Thank you for reminding, the release candidate can’t upload to Nexus at > the moment > > Nexus is not the primary location for a RC it need to be uploaded to [1 > before a vote is caled]. If someone can point me to what is going to be > released I can check it before a vote is called > > I also notice that the current site may need a few changes to comply with > branding policy [2]. It is for example missing a incubating disclaimer so > it's not obvious that this in an incubating project. > > Having a prominent link to GitHub is also not following policy. [3] > > As the project is incubating it’s not expected that it gets everything > correct right away so there’s no issues with any of the above as long as > they are fixed before graduation. > > Thanks, > Justin > > 1. http://www.apache.org/dev/release-distribution#dist-dir > 2. http://incubator.apache.org/guides/branding.html > 3. http://www.apache.org/legal/release-policy.html#what > >
