Fixed everything except for the section headers. I don't think I have any control over this since it's defined by the theme or css of the apache site. At least I haven't yet located another page on www.apache.org that has numbered section headers....but yes it drives me crazy too.
On Tue, Jul 27, 2010 at 12:09 AM, Barrie Treloar <[email protected]> wrote: > On Tue, Jul 27, 2010 at 3:04 AM, Brian Fox <[email protected]> wrote: >> I finally crossed off a todo that was about 12 months old: >> >> I synthesized the various docs we had laying around to produce a >> generic Apache wide release procedure for publishing Maven based >> artifacts via the repository, and updated our Maven Project specific >> docs at the same time. These new docs can be found at: >> >> http://maven.apache.org/developers/release/releasing.html and >> http://www.apache.org/dev/publishing-maven-artifacts.html (note that >> the maven site hasn't refreshed yet, check the date in the top right, >> it should be 7/26 when it's updated) >> >> Let me know if I missed anything. > > That's excellent. > > I especially like the link to auto-create a Jira ticket for enabling a > project to be configured in Nexus. > > I've also checked that all links are working. > > No issues with: > > http://maven.apache.org/developers/release/releasing.html > But I've never followed > http://maven.apache.org/developers/release/maven-proper-release.html > so I can't comment on correctness. > > > Some minor issues: > > http://www.apache.org/dev/publishing-maven-artifacts.html > > Is it possible for the headings to have some formatting (besides smaller > fonts)? > They currently all left align with no section numbering. This make it > difficult to read and determine what is a subsection of what. > > * Seciton 4 - Stage the release for a vote > > Now you must close the staging repository to indicate to Nexus that > the build is done [insert:and to] make the artifacts available. > (Also most people may not be familiar with Nexus, so a brief > explanation of any other options besides closing the staging > repository (or why close is the only option). > I'm not even sure if there is other options, do you always get a fresh > repo when you release and close it when you are done?) > > * Dropping a Repo > > Don't forget to rollback any scm changes. [insert: links to rollback > docs (this happens so infrequently people could use a reminder on what > to do)] > > * mvn release:prepare "commit failed" - svn: Path > 'https://svn.apache.org/repos/asf/maven/plugins/tags/maven-eclipse-plugin-2.7' > already exists > > [insert: Explanation of why/how this happened. (Deleting a tag > scares me and as long as it was something that I did because of a > failed release that ok, I want to make sure I'm not deleting someone > elses tag incorrectly)] > Then the resolution is to delete the tag using: > > Thanks, this is much appreciated. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
