Author: joewitt
Date: Sun Jan 18 20:07:41 2015
New Revision: 1652843
URL: http://svn.apache.org/r1652843
Log:
making progress - still a long ways to go
Modified:
incubator/nifi/site/trunk/content/development/release-guide.md
Modified: incubator/nifi/site/trunk/content/development/release-guide.md
URL:
http://svn.apache.org/viewvc/incubator/nifi/site/trunk/content/development/release-guide.md?rev=1652843&r1=1652842&r2=1652843&view=diff
==============================================================================
--- incubator/nifi/site/trunk/content/development/release-guide.md (original)
+++ incubator/nifi/site/trunk/content/development/release-guide.md Sun Jan 18
20:07:41 2015
@@ -42,16 +42,31 @@ capacity of a [Release Manager][release-
- [Apache Release Signing][apache-release-signing]
- [Apache Guide to publish Maven Artifacts][apache-guide-publish-maven]
-## The Objective
+## The objective
+
+Our aim is to produce and official Apache release.
+The following is a list of the sorts of things that will be validated:
+
+ - Do the resulting artifacts have 'incubating' in the name?
+ - Is the LICENSE and NOTICE file present in the source root and complete?
+ - Is the DISCLAIMER present with the LICENSE and NOTICE?
+ - Is there a README available that explains how to build the application and
to execute it?
+ - Are the signatures and hashes correct for the source release?
+ - Do all sources have necessary headers?
+ - Are there no unexpected binary files in the release?
+ - Can one compile and run the application with tests from the source bundle?
+
+## The flow of a release (an outline)
+ - The community is contributing to a series of JIRA tickets assigned to the
next release
+ - The number of tickets open/remaining for that next release approaches zero
+ - A member of the community suggests a release and initiates a discussion
+ - Someone volunteers to be an RM for the release (can be a committer but
apache guides indicate preference is a PPMC member)
+ - A release candidate is put together and a vote sent to the team.
+ - If the team rejects the vote the issues noted are resolved and another RC
is generated
+ - Once a vote is accepted within the NiFi PPMC for a release candidate then
the vote is sent to the IPMC
+ - If the IPMC rejects the vote then the issues are resolved and a new RC
prepared and voted upon within the PPMC
+ - If the IPMC accepts the vote then the release is 'releasable' and can be
placed into the appropriate 'dist' location, maven artifacts released from
staging.
-So with all the background material in mind and with the intent to perform
-a release established it is important to acknkowledge the objective here.
-The aim is to produce an official Apache release. That means producing a
legally
-valid and signed bundle of source code which one can download and build for
themselves.
-The other items like prebuilt binaries of the full application are not the
official
-release artifact they are conveniences for users who cannot readily build the
application
-themselves. The same is true then of maven artifacts published to Apache or
-mirrored artifact repositories.
[release-manager]:
http://www.apache.org/dev/release-publishing.html#release_manager
[apache-license]: http://apache.org/licenses/LICENSE-2.0
