Differences between revisions 6 and 7
Revision 6 as of 2005-06-08 04:15:51
Size: 8165
Editor: 63
Comment:
Revision 7 as of 2005-08-18 22:03:52
Size: 3474
Editor: lc-ez-63-96-185-209
Comment: this is the first cut of release criteria for Beehive v1
Deletions are marked like this. Additions are marked like this.
Line 2: Line 2:
''Author: Steve Tocco Last Revised Date: 5/18/05, Version 1.0''
Line 3: Line 4:
''Author: Steve Tocco Last Revised Date: 5/4/05, Version 1.10'' This document outlines all of the release criteria to be satisfied so Beehive 1.0 can be released.
Line 5: Line 6:
This document outlines all of the release criteria to be satisfied before Beehive 1.0 can be released. This document does not address elements to specifically get Beehive 1.0 out of Incubation at Apache, but some of these milestones may be used in defense of that position.

So here is the proposed list of release criteria for v1 Beehive. In the remainder of this document, the Subversion revision number that
(eventually) reflects Beehive 1.0 will be simply referred to as the release candidate.
In the remainder of this document, the Subversion revision number that
(eventually) reflects Beehive 1.0 will be simply referred to as the '''release candidate'''.
Line 13: Line 12:
'''SOURCE TREE'''
The following indicate activities that must occur in the Beehive Subversion Source Tree before we are ready to ship Beehive 1.0.

#1.0 [[BR]]
Objective: All DRTs/Checkin tests pass at 100% when executed against the release candidate revision number in the source tree.[[BR]]
Background: All DRTs must pass at 100% for NetUI, JWS and Controls.[[BR]]
Gating: Yes [[BR]]
Owner(s): [[BR]]

#1.1[[BR]]
Objective: All BVT/detailed tests pass at 100% when executed against the
release candidate revision number in the source tree. [[BR]]
Background: Any BVTs/detailed tests not passing should have JIRA issue filed and be commented out for the release candidate. If at a later date a fix is to be added to 1.0 (something like 1.0.1) the test can be re-enabled in the 1.0 branch or in the next major release (1.1 or 2.0) [[BR]]
Gating: Yes [[BR]]
Owner(s): [[BR]]

#1.2[[BR]]
Objective: Any tests commented out due to failures should have JIRA issues filed (defects or enhancements) to be fixed in subsequent releases. Comments within test configuration files should indicate the JIRA issue tracking the problem.[[BR]]
Background: N/A [[BR]]
Gating: Yes[[BR]]
Owner(s):[[BR]]

#1.3[[BR]]
Objective: The website content must be generated in support of the release candidate.[[BR]]
Background: N/A[[BR]]
Gating: Yes[[BR]]
Owner(s):[[BR]]

#1.4[[BR]]
Objective: The javadoc target for the release candidate must be able to pass successfully.
Background: We must be able to successfully build the javadoc.[[BR]]
Gating: Yes[[BR]]
Owner(s):[[BR]]

#1.5[[BR]]
Objective: JSF integration tests must pass at 100%.[[BR]]
Background: We must be able to pass these tests. Failures have JIRA issue tagged and filed for next release and test commented out of run.[[BR]]
Gating: Yes[[BR]]
Owner(s):[[BR]]

'''DISTRIBUTION BITS'''[[BR]]
The following indicate activities that must occur in support of the Beehive Distribution.[[BR]]

#2.0[[BR]]
Objective: The Beehive Distribution must be able to be created from the release candidate.[[BR]]
Background: We must be able to build the distribution from the release candidate.[[BR]]
Gating: Yes[[BR]]
Owner(s):[[BR]]

#2.1[[BR]]
Objective: The Beehive Test Distribution must be able to be created from the release candidate.[[BR]]
Background: We must be able to build the test distribution from the release candidate. This is really needed to verify bits in the distribution.[[BR]]
Gating: Yes[[BR]]
Owner(s):[[BR]]

#2.2[[BR]]
Objective: All tests (DRTs/checkin/BVTs/detailed) in support of Beehive must be able to be executed from the test distribution against the distribution derived from the release candidate.[[BR]]
Background: Thus test code must fully be enabled to run in this manner.[[BR]]
Gating: Yes[[BR]]
Owner(s):[[BR]]

#2.3[[BR]]
Objective: All DRTs/Checkin tests must pass at 100% when executed from the test distribution against the distribution for the release candidate for Windows 2003 Server.[[BR]]
Background: We need the same pass rate to verify it is a good distribution.[[BR]]
Gating: Yes[[BR]]
Owner(s):[[BR]]

#2.4[[BR]]
Objective: All DRTs/Checkin tests must pass at 100% when executed from the test distribution against the distribution for the release candidate for Redhat Linux AS 3.0.[[BR]]
Background: We need the same pass rate to verify it is a good distribution.[[BR]]
Gating: Yes[[BR]]
Owner(s):[[BR]]

#2.5[[BR]]
Objective: All BVT/Detailed tests must pass at 100% when executed from the test distribution against the distribution for the release candidate for Window 2003 Server.[[BR]]
Background: We need the same pass rate to verify it is a good distribution.[[BR]]
Gating: Yes[[BR]]
Owner(s):[[BR]]

#2.6[[BR]]
Objective: All BVT/Detailed tests must pass at 100% when executed from the test distribution against the distribution for the release candidate for Redhat Linux AS 3.0.[[BR]]
Background: We need the same pass rate to verify it is a good distribution.[[BR]]
Gating: Yes[[BR]]
Owner(s):[[BR]]

#2.7[[BR]]
Objective: The distribution created from the release candidate must be published for download and signed.[[BR]]
Background: N/A[[BR]]
Gating: Yes[[BR]]
Owner(s):[[BR]]

'''RELEASE PLANNING'''[[BR]]
The following indicate activities that must occur in support of the Beehive Distribution for Release Planning.[[BR]]

#3.0[[BR]]
Objective: The release candidate needs to be proposed for vote within Apache. This needs to be a minimum of three days prior to release and needs to include all documentation, tests.[[BR]]
Background: We should not go to vote until all docs are ready including samples, user guides, java doc, etc.[[BR]]
Gating: Yes[[BR]]
Owner(s):[[BR]]

#3.1[[BR]]
Objective: The vote submitted for the release candidate must pass.[[BR]]
Background: N/A[[BR]]
Gating: Yes[[BR]]
Owner(s):[[BR]]

#3.2[[BR]]
Objective: Release Notes must be produced and published in support of the release candidate. This should capture:
 * A release description. Daryl says it best: "This would describe the overall goals of the release (feature work, bug fix work, etc). In addition, it would be nice if each release had a bit of a road map for the expectations and time frame is for the next release in the line. In addition, if the release is a branch from some release, the relationship of the release with the branches should be described."
 * A list of new features.
 * A list (JIRA links) of issues fixed since the last release. This need not include documentation bugs.
 * A list (JIRA links) of known/unresolved issues. This need not include documentation bugs.
Background: Should be published as part of the dist itself.[[BR]]
Gating: Yes[[BR]]
Owner(s):[[BR]]

#3.3[[BR]]
Objective: For the release candidate, no open bugs will exist. All items will be fixed or assigned to the new release.[[BR]]
Background: Currently all things for the future are assigned to Fix For version equal to "TBD".[[BR]]
Gating: No[[BR]]
Owner(s):


'''DOCUMENTATION'''[[BR]]
#4.0[[BR]]
Objective: All samples must be completed for the release candidate. The samples list includes: [[BR]]
   1) Petstore [[BR]]
   2) External config feature samples [[BR]]
   3) DB control [[BR]]
   4) Service control [[BR]]
   5) JSF sample[[BR]]
Background: List may grow.[[BR]]
Gating: Yes[[BR]]
Owner(s):[[BR]]

#4.1[[BR]]
Objective: All samples must be part of the distribution for the release candidate.
Background: These need to be proofed and executed.[[BR]]
Gating: Yes[[BR]]
Owner(s):[[BR]]

#4.2[[BR]]
Objective: All Java Doc for "Public Use" APIs must be authored as part of the release candidate.
Background: This is mainly a driver to indicate if there is any API that we intend users to implement/understand, Javadoc must be provided.[[BR]]
These need to be authored/proofed by developers.[[BR]]
Gating: Yes[[BR]]
Owner(s):[[BR]]

#4.3[[BR]]
Objective: All tutorials on the website must be able to be successfully executed against the distribution created from the release candidate.[[BR]]
Background: N/A[[BR]]
Gating: Yes [[BR]]
Owner(s):[[BR]]

#4.4[[BR]]
Objective: The Beehive website must be updated to support the release candidate, including samples, download information, etc.[[BR]]
Background: N/A[[BR]]
Gating: Yes[[BR]]
Owner(s):[[BR]]
|||||| '''SOURCE TREE'''||
||Number||Objective||Background||
||1.0||All DRTs/Checkin tests pass at 100% when executed against the release candidate revision number in the source tree.||All DRTs must pass at 100% for NetUI, and Controls. JWS is not required.||
||1.1||All BVT tests pass at 100% when executed against the release candidate revision number in the source tree.||Any BVTs not passing should have JIRA issue filed and be commented out for the release candidate. If at a later date a fix is to be added to 1.0 (something like 1.0.1) the test can be re-enabled in the 1.0 branch or in the next major release (1.1 or 2.0). JWS is not required.||
||1.2||Any tests commented out due to failures should have JIRA issues filed (defects or enhancements) to be fixed in subsequent releases. Comments within test configuration files should indicate the JIRA issue tracking the problem.|| ||
||1.3||The javadoc target for the release candidate must be able to pass successfully.||We must be able to successfully build the javadoc.||
||1.4||JSF integration tests must pass at 100%.||Not part of normal BVT target.||
|||||| '''DISTRIBUTION BITS'''||
||2.0||The Beehive Distribution must be able to be created from the release candidate.||We must be able to build the distribution from the release candidate.||
||2.1||The Beehive Test Distribution must be able to be created from the release candidate.||We must be able to build the test distribution from the release candidate.||
||2.2||All tests (DRTs/checkin/BVTs/detailed) in support of Beehive must be able to be executed from the test distribution against the distribution derived from the release candidate.||Thus test code must fully be enabled to run in this manner.||
||2.3||The distribution created from the release candidate must be published for download and signed.|| ||
|||||| '''RELEASE PLANNING'''||
||3.0||A list of known issues must be produced and published in support of the release candidate. This should capture all known defects (from JIRA) the user may encounter. This need not include enhancements and documentation bugs.||Could be published as part of the dist itself or perhaps on the Beehive website. If part of the dist, must be made before the vote.||
||3.1||For the release candidate, no open bugs will exist. All items will be fixed or assigned to the new release.||Currently all things for the future are assigned to Fix For version equal to “TBD”.||
||3.2||For the release candidate, no resolved bugs will exist. All items will be fixed or assigned to the new release.||There are some exceptions for this for code that is not shipping such as WSM and src tree only infrastructure.||
|||||| '''DOCUMENTATION'''||
||4.0||All Java Doc for “Public Use” APIs must be authored as part of the release candidate.||This is mainly a driver to indicate if there is any API that we intend users to implement/understand, Javadoc must be provided.||

BEEHIVE 1.0 RELEASE CRITERIA Author: Steve Tocco Last Revised Date: 5/18/05, Version 1.0

This document outlines all of the release criteria to be satisfied so Beehive 1.0 can be released.

In the remainder of this document, the Subversion revision number that (eventually) reflects Beehive 1.0 will be simply referred to as the release candidate.

The release criteria generally fall into one of the following areas: Source Tree, Distribution Bits, Release Planning, and Documentation.

SOURCE TREE

Number

Objective

Background

1.0

All DRTs/Checkin tests pass at 100% when executed against the release candidate revision number in the source tree.

All DRTs must pass at 100% for NetUI, and Controls. JWS is not required.

1.1

All BVT tests pass at 100% when executed against the release candidate revision number in the source tree.

Any BVTs not passing should have JIRA issue filed and be commented out for the release candidate. If at a later date a fix is to be added to 1.0 (something like 1.0.1) the test can be re-enabled in the 1.0 branch or in the next major release (1.1 or 2.0). JWS is not required.

1.2

Any tests commented out due to failures should have JIRA issues filed (defects or enhancements) to be fixed in subsequent releases. Comments within test configuration files should indicate the JIRA issue tracking the problem.

1.3

The javadoc target for the release candidate must be able to pass successfully.

We must be able to successfully build the javadoc.

1.4

JSF integration tests must pass at 100%.

Not part of normal BVT target.

DISTRIBUTION BITS

2.0

The Beehive Distribution must be able to be created from the release candidate.

We must be able to build the distribution from the release candidate.

2.1

The Beehive Test Distribution must be able to be created from the release candidate.

We must be able to build the test distribution from the release candidate.

2.2

All tests (DRTs/checkin/BVTs/detailed) in support of Beehive must be able to be executed from the test distribution against the distribution derived from the release candidate.

Thus test code must fully be enabled to run in this manner.

2.3

The distribution created from the release candidate must be published for download and signed.

RELEASE PLANNING

3.0

A list of known issues must be produced and published in support of the release candidate. This should capture all known defects (from JIRA) the user may encounter. This need not include enhancements and documentation bugs.

Could be published as part of the dist itself or perhaps on the Beehive website. If part of the dist, must be made before the vote.

3.1

For the release candidate, no open bugs will exist. All items will be fixed or assigned to the new release.

Currently all things for the future are assigned to Fix For version equal to “TBD”.

3.2

For the release candidate, no resolved bugs will exist. All items will be fixed or assigned to the new release.

There are some exceptions for this for code that is not shipping such as WSM and src tree only infrastructure.

DOCUMENTATION

4.0

All Java Doc for “Public Use” APIs must be authored as part of the release candidate.

This is mainly a driver to indicate if there is any API that we intend users to implement/understand, Javadoc must be provided.

V1ReleaseCriteria (last edited 2009-09-20 23:24:30 by localhost)