1. petsc
  2. PETSc
  3. petsc

Commits

Jed Brown  committed 8bb363b

How to follow 'master', 'next', and 'maint'

  • Participants
  • Parent commits 03ae9c6
  • Branches master

Comments (0)

Files changed (1)

File Home.md

View file
  • Ignore whitespace
+# Following PETSc development
+The default branch in the PETSc repository is named [`master`](https://bitbucket.org/petsc/petsc/commits/all/tip/master).
+It contains all features and bug fixes that are believed to be stable and will be in the next release.
+Users developing software based on recently-added features in PETSc should follow `master`:
+
+    $ git clone https://bitbucket.org/petsc/petsc
+    $ cd petsc
+    $ git pull               # to get updates
+
+Features that are still experimental will be in the [`next`](https://bitbucket.org/petsc/petsc/commits/all/tip/next) branch.
+To use these features, and perhaps influence their design, follow `next` and discuss your concerns on the [petsc-dev mailing list](http://lists.mcs.anl.gov/pipermail/petsc-dev/) or by commenting on commits. After cloning, use
+
+    $ git checkout next
+    $ git pull               # to get updates
+
+You can `git checkout master` to get back to the more stable version.
+
+Production users can follow the `maint` branch which contains the latest maintenance release plus any additional bug fixes.
+This should always be more stable than the latest tarball.
+
 # Contributing to PETSc
 
 The most efficient way to create any patch or new functionality is to use a version control system. We recommend Git, but can also deal with Mercurial.