accumulo-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From els...@apache.org
Subject svn commit: r1646503 - /accumulo/site/trunk/content/governance/releasing.mdtext
Date Thu, 18 Dec 2014 18:18:42 GMT
Author: elserj
Date: Thu Dec 18 18:18:42 2014
New Revision: 1646503

URL: http://svn.apache.org/r1646503
Log:
Remove old versioning guidelines

Modified:
    accumulo/site/trunk/content/governance/releasing.mdtext

Modified: accumulo/site/trunk/content/governance/releasing.mdtext
URL: http://svn.apache.org/viewvc/accumulo/site/trunk/content/governance/releasing.mdtext?rev=1646503&r1=1646502&r2=1646503&view=diff
==============================================================================
--- accumulo/site/trunk/content/governance/releasing.mdtext (original)
+++ accumulo/site/trunk/content/governance/releasing.mdtext Thu Dec 18 18:18:42 2014
@@ -17,34 +17,9 @@ Notice:    Licensed to the Apache Softwa
            specific language governing permissions and limitations
            under the License.
 
-Accumulo works on a very simple cycle of major releases with the minor releases when needed.
The intent is for all major features to be implemented in a major release, with only bug fixes
and minor features being included in minor releases. API changes should only be made on major
releases, with continued support of the previous API for at least one major revision. This
will give user code a major revision to convert from the old API to the new API.
+## Versioning
 
-Note: There will be times where API compatibility cannot be maintained, which we understand.
However, this should only be considered when there is NO other option.
-
-
-## Major Release
-
-  1. Vote to start the major release process.  This should be in consensus with the community
and should be discussed on the accumulo-dev mailing list before the next steps take place.
The majority of the committers must +1 the vote and all -1s need to be discussed.
-    - There is not a strict time limit between major releases, but some consideration should
be made because we don't want to give our early adopters version fatigue.
-    - This will be the feature freeze for the version. Any features considered after this
call need a very strong reason for implementation, which can be discussed via mailing list.
-  - Create a JIRA version for the proceeding release number. This is so we can begin the
process of noting which features are bound for the current trunk vs. a future version.
-  - Handle all JIRA tickets assigned for the current major release version. Any ticket whose
version is changed should have an explanation of why it is not to be handled in the current
release.
-  - Once all JIRA tickets against the codebase (except documentation tickets) are resolved/redirected,
the code will be branched in SVN.
-    - While there is currently a new trunk for the next release, it is highly discouraged
to begin committing new features to it because this is when the current release is being tested.
Any major bugs found will have to be patched in both versions and we want to make the process
as seamless as possible.
-    - The new trunk needs to have its version information updated.
-  - Wrap up any standing documentation endeavors, whether or not there are tickets for them.
-  - Analyze API changes since last major release and ensure there are no changes that will
cause pain for users.
-  - Analyze and update dependencies (e.g. with mvn dependency:analyze)
-  - Test the branch as per our testing criteria.
-  - Once testing is deemed successful and release documentation is complete, move on to Releasing.
-
-## Minor Release
-
-  1. Upon detection and/or resolution of a bug, discussion needs to be made on the accumulo-dev
list to determine if the community thinks the bug is critical or if there have been sufficient
minor bug fixes to warrant a minor release.
-  - Make any necessary documentation changes, including a change log.
-  - Analyze and update dependencies (e.g. with mvn dependency:analyze)
-  - Test the now updated branch as per our testing criteria.
-  - Once testing is deemed successful and documentation is complete, move on to Releasing.
+Accumulo has adopted [Semantic Versioning][1] and follows their rules and guidelines.
 
 ## Testing
 
@@ -85,4 +60,6 @@ The following tests require a Hadoop clu
   - A vote must be made on dev@accumulo. Lazy consensus is not sufficient for a release;
at least 3 +1 votes from PMC members are required. All checksums and signatures need to be
verified before any voter can +1 it. Voting shall last 72 hours.
     - Voters SHOULD include with their vote details on the tests from the testing section
they have successfully run. If given, said details for each test MUST include: the number
of worker nodes in the cluster, the operating system and version, the Hadoop version, and
the Zookeeper version.  For testing done on a version other than the release candidate that
is deemed relevant, include the commit hash. All such gathered testing information will be
included in the release notes. 
   - Upon successful vote, the new releases can be retagged to remove the RC status and released
on the Accumulo webpage.
-  - If at any time the tag needs to be remade due to any sort of error, it should be incremented
to the next release candidate number.
\ No newline at end of file
+  - If at any time the tag needs to be remade due to any sort of error, it should be incremented
to the next release candidate number.
+
+[1]: /versioning.html
\ No newline at end of file



Mime
View raw message