Spring/spring-data-build
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

#340 - Added section with dependency compatibility guidelines in release trains.

Browse Source
This commit is contained in:
Oliver Gierke
2017-04-19 15:55:10 +02:00
parent 9a331c7afa
commit 892a60e48d
1 changed files with 6 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
CONTRIBUTING.adoc
View File

@@ -56,6 +56,12 @@ This section contains some advanced information, mainly targeted at developers o
* Try to keep the lifespan of a feature branch as short as possible. For simple bug fixes they should only be used for code review in pull requests.
* On longer running feature branches, don't pull changes that were made to master in the meantime. Instead, rebase the feature branch onto current master, sorting out issues and making sure the branch will fast-forward merge eventually.
[[advanced.dependency-management]]
=== Dependency management
* When upgrading dependencies of a project, make sure you apply the following rules:
** For service releases of a release train only upgrades to bugfix versions are allowed. I.e. if a GA release of a release train included a dependency in version 2.6.2, you must only upgrade to 2.6.x versions. Upgrading to 2.7 is *not allowed*.
** During the milestone phase of a new release train, upgrade to the latest version of a dependency unless compatibility with a former version is required. Upgrades to new major versions are allowed, too, but consider ways to support multiple major versions for one release train to allow a smoother transition.
[[advanced.change-tracking]]
=== Change tracking