river-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From sijs...@apache.org
Subject svn commit: r1032771 - /incubator/river/site/trunk/content/development-process.mdtext
Date Mon, 08 Nov 2010 22:22:32 GMT
Author: sijskes
Date: Mon Nov  8 22:22:32 2010
New Revision: 1032771

URL: http://svn.apache.org/viewvc?rev=1032771&view=rev
small fixes


Modified: incubator/river/site/trunk/content/development-process.mdtext
URL: http://svn.apache.org/viewvc/incubator/river/site/trunk/content/development-process.mdtext?rev=1032771&r1=1032770&r2=1032771&view=diff
--- incubator/river/site/trunk/content/development-process.mdtext (original)
+++ incubator/river/site/trunk/content/development-process.mdtext Mon Nov  8 22:22:32 2010
@@ -3,7 +3,7 @@ Title: Development Process
 # River Development Process
-### Tracking issues and changes
+## Tracking issues and changes
 * A JIRA issue is required for any substantive change.
 In order to keep the list of JIRA issues under control, it is expected that any controversial
issue or user request for a feature or design change be discussed on the dev list prior to
entering it into JIRA.
@@ -11,7 +11,7 @@ In order to keep the list of JIRA issues
 * Issue discussions
 The preferred place of discussion on issues is the river-dev mail list. A link to the beginning
of the mail thread on the issue should be placed in the JIRA issue so that users looking through
JIRA can easily view the thread of discussion on an issue. Please keep the Subject line the
same so that the email thread hangs together.  It's also recommended that a summary/conclusion
on the thread be recorded in the JIRA issue itself.
-#### Handling Security -related Issues
+## Handling Security -related Issues
 There are three options associated with the "Security Level" field in the JIRA instance:
 * "None"
@@ -24,7 +24,7 @@ If the issue is acknowledged as a valid 
 As soon as appropriate (for example, when the impact is understood and/or there is a resolution/fix
developed), the "Security Level" should be changed to "Security risk, visible to anyone" and
an explanation/discussion should occur in the broader River community on the river-dev list.
-### Code Reviews
+## Code Reviews
 * for public API changes:
 [RTC](http://apache.org/foundation/glossary.html#ReviewThenCommit) These changes have potentially
broad effects on developers and users, and therefore will require a code review and vote.
Since some of these changes will affect the API docs ('specs'), everyone within the Jini/River
community is encouraged to review and vote. The Committer votes are binding, but the sentiment
of the entire community will be strongly considered.
@@ -32,11 +32,11 @@ As soon as appropriate (for example, whe
 * for all other changes:
 [CTR](http://apache.org/foundation/glossary.html#CommitThenReview) Although CTR is what is
specified, developers should feel comfortable requesting the list for peer review before committing.
-### Testing
+## Testing
 Developing test cases and running test suites are desired but not required prior to an integration.
 If unit tests are created for a change, the developer is encouraged to add them to the JIRA
issue for sharing.
-### Version Numbering
+## Version Numbering
 Each Apache River deliverable has a version number of:
@@ -49,7 +49,7 @@ Each Apache River deliverable has a vers
 The major version number will in general only be increased in case of major changes that
might introduce compatibility problems or represent some fundamental improvements. The minor
versions reflect the various feature releases, the last part of the version number reflects
the maintenance release.
-### Branching Policy
+## Branching Policy
 Ongoing development for the next release takes place in the {{/trunk}}. Once feature complete
for a (non maintenance) release the trunk is branched into {{/branches/<m.n>}} which
in general also reflects the moment a release candidate is presented to the public in a fairly
short period of time. Ongoing development continues in the {{/trunk}}, issues found against
the release candidate will be fixed in {{/branches/<m.n>}} and likely merged into the
@@ -88,4 +88,4 @@ Although ongoing development should take
    |         \ -------  /tags/3.0.0/
    |          \
    |           \ -------  /tags/3.0.1/
\ No newline at end of file

View raw message