Author: bimargulies
Date: Thu Jan 15 14:03:37 2015
New Revision: 1652101
URL: http://svn.apache.org/r1652101
Log:
Add initial release procedure boilerplate
Added:
incubator/nifi/site/trunk/content/development/releasemanagement.mdtext
(with props)
Added: incubator/nifi/site/trunk/content/development/releasemanagement.mdtext
URL:
http://svn.apache.org/viewvc/incubator/nifi/site/trunk/content/development/releasemanagement.mdtext?rev=1652101&view=auto
==============================================================================
--- incubator/nifi/site/trunk/content/development/releasemanagement.mdtext
(added)
+++ incubator/nifi/site/trunk/content/development/releasemanagement.mdtext Thu
Jan 15 14:03:37 2015
@@ -0,0 +1,39 @@
+Title: Release Management
+Notice: Licensed to the Apache Software Foundation (ASF) under one
+ or more contributor license agreements. See the NOTICE file
+ distributed with this work for additional information
+ regarding copyright ownership. The ASF licenses this file
+ to you under the Apache License, Version 2.0 (the
+ "License"); you may not use this file except in compliance
+ with the License. You may obtain a copy of the License at
+ .
+ http://www.apache.org/licenses/LICENSE-2.0
+ .
+ Unless required by applicable law or agreed to in writing,
+ software distributed under the License is distributed on an
+ "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+ KIND, either express or implied. See the License for the
+ specific language governing permissions and limitations
+ under the License.
+
+# Release Management #
+
+The NiFi project follows the usual Apache Software Foundation conventions for
managing releases of projects
+built with Apache Maven. These are documented on this page: [Maven Releases at
Apache][1].
+
+As of this writing, NiFi releases two things: the `nar-maven-plugin` and NiFi
proper. Each release requires the full
+ASF release procedure, summarized here. Releases are performed by a volunteer
release manager. Any committer
+may serve as a release manager.
+
+
+ 1. Interact with the dev@ community to give people a fair chance to get 'one
more commit' in before a release.
+ 2. Stage the release, as described in the page linked above.
+ 3. Start a vote for the release on dev@. See [how the Maven project][2] words
email for a template until someone
+at NiFi gets around to writing something more specific.
+ 4. Be sure that the vote is copied to the general@incubator as per incubator
rules.
+ 5. If the vote passes: (a) promote the Maven artifacts by interacting with
repository.apache.org, and (b) get the
+official release artifact copied to the dist area.
+6. If the vote fails (sigh) drop the staging repository.
+
+ [1]: http://www.apache.org/dev/publishing-maven-artifacts.html
+ [2]:
http://maven.apache.org/developers/release/maven-project-release-procedure.html
\ No newline at end of file
Propchange:
incubator/nifi/site/trunk/content/development/releasemanagement.mdtext
------------------------------------------------------------------------------
svn:eol-style = native
