General mailing list for discussions and development of PeerLibrary and related software.

List archive Help


[PeerLibrary dev] Change in main development branch


Chronological Thread 
  • From: Mitar < >
  • To: PeerLibrary development < >
  • Subject: [PeerLibrary dev] Change in main development branch
  • Date: Tue, 29 Apr 2014 03:52:11 -0700

Hi!

With 0.2 release we will start developing really according to our
development model:

https://github.com/peerlibrary/peerlibrary/wiki/Development-Model

This means that all development and all pull requests should happen
against *development* branch. master branch should always be the latest
stable version. (So released version + bugfixes.) Whatever we push into
master we will have to support (and create migrations for). Whatever we
push into development we can still change before releasing it.

development branch is called "integration" branch into which all feature
branches (branches we make when changing something) are merged. Then,
from time to time and when we test development branch, we release a new
version by merging it into master.

While we are developing a new version we can bugfix smaller things in
master branch (or backport those from development branch).


Mitar

--
http://mitar.tnode.com/
https://twitter.com/mitar_m


  • [PeerLibrary dev] Change in main development branch, Mitar, 04/29/2014

Archive powered by MHonArc 2.6.18.

Top of page