River Development Process¶
River build server¶
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.
JIRA issues are not needed for small (e.g., typos) changes.
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¶
There are three options associated with the "Security Level" field in the JIRA instance: "None" "Security risk, visible to committers" - only committers have access to the issue with this option set * "Security risk, visible to anyone" - the issue has a security risk associated with it, and the committers understand the impact. A resolution/fix has been developed.
When a potential security -related issue is identified in the River sourcebase, initial discussion on it should occur on the private PPMC list. If the person(s) who identified the issue are not on the PPMC, they should be included in the discussion.
If the issue is acknowledged as a valid security issue, a JIRA issue needs to be created with the "Security Level" field marked to "Security risk, visible to committers".
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.
for public API changes: RTC 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.
for all other changes: CTR Although CTR is what is specified, developers should feel comfortable requesting the list for peer review before committing.
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.
Here is a list of individually executable test categories.
Each Apache River deliverable has a version number of:
m= major version
n= minor version
r= maintenance version
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.
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
Once a release candidate is ready for a first customer release
/branches/<m.n> is branched into
/tags/<m.n>.0. When support is required for a particular release
m.n, the development for a fix-release is conducted in
/branches/<m.n>. When a bug-fix release is ready it is branched into
r is a positive number and increased for each maintenance release.
Although ongoing development should take place in
/trunk, there is a
/skunk branch that can be utilized for 'experimental' work that must not disturb the
/trunk, that needs to be visible to others and/or might require participation of others. In general the lifetime of such branch should be short to give it a chance of successful integration into the
/trunk when the 'experiment' has been found valuable.
||frozen release tags|
||development and 'skunk works' branches|
/trunk | |-------- /branches/2.1/ | \ | \ ------- /tags/2.1.0/ | \ | \ ------- /tags/2.1.1/ | \ | |-------- /branches/2.2/ | \ | \ ------- /tags/2.2.0/ | \ | |-------- /skunk/
| | |-------- /branches/3.0/ | \ | \ ------- /tags/3.0.0/ | \ | \ ------- /tags/3.0.1/
Tabs are not used. Default indentation is 4 spaces.
Contributors are advised to read the Code Conventions for the Java and try to adhere as much as possible to these conventions.
If the reformatting involves a large part of the code, a clearly labeled 'reformatting' commit in between is recommended. Keeping your reformatting changes limited, reduces the change of merging conflicts by your fellow committers.
We do not actively search and reformat source files that are not formatted according to this convention.
Older sources are best viewed with tab stops at 8 space intervals.