Skip to content

Instantly share code, notes, and snippets.

@ivarne

ivarne/Backporting policy.md

Last active August 29, 2015 14:10
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save ivarne/6624e456889f5d23ed36 to your computer and use it in GitHub Desktop.
Save ivarne/6624e456889f5d23ed36 to your computer and use it in GitHub Desktop.
Download ZIP
Raw
Backporting policy.md

Backporting policy

Becasue Julia is in rapid development and we need the freedom to to backwards incompatible changes on the master branch, the Julia community has decided that we want to do regular releases for people who wants a more stable enviroment to get the Julia experience. As bugs are discovered in the released versions, we will make a best effort attempt to fix them and release bugfix releases. We call this process backporting because usually it involves cherry-picking commits from the master branch onto the release branch.

Backwards Compatibility

  1. The fundamental rule for compatibility is that a program that doesn't rely on something we consider a bug (eg. exceptions and wrong method results), that works on 0.3.x must work without modification on 0.3.y where y > x.

Forwards compatibility

  1. New APIs and functionalities in master can (if possible without breaking 1.) be backported to release-0.x, to simpelify writing code that runs on
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment