In this document the Eclipse RDF4J project workflow and developer best practices are explained. It contains information on how to create branches, tag releases, manage pull requests, create and schedule issues, and so on.
Some of this information is targeted specifically at the project lead(s), other information is relevant to every committer.
RDF4J strives to apply Semantic Versioning principles to its development:
We allow changes to public or protected methods/classes/interfaces in minor releases under the following conditions:
@InternalUseOnlyis not considered part of the public API, and may be changed in a minor release.
For patch releases we never allow changes in the public API, unless the change is specifically to fix a bug that aligns the actual behavior of the code with the publicly documented behavior.
The main branches (
develop) use a SNAPSHOT version number to indicate that they are snapshots on the road to the next version. The
main version always has the same major and minor number as the latest release, with the patch version incremented by one: for example if the latest release was 3.1.0, the
main version will be 3.1.1-SNAPSHOT. The
develop version uses the next expected major/minor release number, for example 3.2.0-SNAPSHOT.
Every issue, no matter how small, gets its own issue
ticket, and its own branch while
under development. The milestone label of the issue is set to the planned
release version for the issue, but that could change by the time a PR is
merged. Issue branch names are always prefixed with
followed by one or two dash-separated keywords for the issue.
GH-1664-transformation-servlet is the branch for a fix for issue
GH-1664, which has to do with the transformation servlet.
RDF4J uses a git branching model where collaborative feature development takes
place on branches from the
develop branch. This is where all development for
the next (minor or major) release happens. The
main branch is reserved for
small bug fixes (to be released in patch/service releases) only.
Once a issue is complete and tested, a Pull Request (PR) should be created for peer review. Like the feature branch to which it corresponds, a Pull Request should be a self-contained change, that is it fixes a single issue. Don’t be tempted to fix several unrelated issues in a single PR please.
The Pull Request description should start with a link to the
issue that is addressed by the PR. If the issue is a new feature or improvment,
the PR should target the
develop branch. If the issue is a bug fix, the PR
should be branched from (and target) the
Tip: when starting work on an issue, and you are unsure if it will be a new
feature or “just” a bug fix, start by branching from the
main branch. It
will always be possible to merge your issue branch into
develop later if
necessary. However, if you start from
develop, merging into
main will not
be possible, and you’re therefore committed to the next minor/major release.
RDF4J uses ‘merge-commits’ as its pull request merge strategy. We aim to achieve a clean but accurate history. Read more about our strategy and the motivation for it in this article: RDF4J merge strategy.
For step-by-step instructions on how to create contributions, see the contributor guidelines.
Some generic sources of information about projects hosted by Eclipse:
Table of Contents
Back to the top