Jump to content

Code Repository: Difference between revisions

From Sahana Eden Wiki
No edit summary
 
(3 intermediate revisions by the same user not shown)
Line 9: Line 9:
==== dev ====
==== dev ====


The ''dev'' branch holds the latest <u>development version</u>. Developers should target this branch, and would normally submit their pull requests there.
The ''dev'' branch holds the latest <u>development version</u>. Contributors should target this branch, and would normally submit their pull requests there.


==== maintenance ====
==== maintenance ====


This branch serves as a staging area for <u>maintenance updates</u> to the current stable version, e.g. bug fixes or enhancements backported from the dev branch. Pull requests will be accepted if they resolve a reported issue that has already been resolved - or become irrelevant - in the ''dev'' branch.
The ''maintenance'' branch serves as a staging area for <u>maintenance updates</u> to the current stable version, e.g. bug fixes or enhancements backported from the ''dev'' branch. The ''dev'' branch must be successfully rebased on this branch before the fixes can be merged into ''master''.


==== v* ====
==== v* ====


These branches contain previous versions, e.g. v4 holds release 4.5, which is the latest release of version 4. These branches can be used for study, historic reference and support, but are not part of the development or release process.
These branches contain previous versions, e.g. v4 holds release 4.5, which is the latest release of version 4. These branches can be used for study, historic reference and support, but are not part of the development or release process.

Latest revision as of 20:14, 18 September 2025

GitHub

The code for Sahana Eden is hosted on GitHub at github.com/sahana/eden. This repository contains several branches:

master

The master branch holds the current stable version of the Eden code, and is intended for deployment or downstream development. It will only be updated by the release process, no pull requests are accepted for this branch.

dev

The dev branch holds the latest development version. Contributors should target this branch, and would normally submit their pull requests there.

maintenance

The maintenance branch serves as a staging area for maintenance updates to the current stable version, e.g. bug fixes or enhancements backported from the dev branch. The dev branch must be successfully rebased on this branch before the fixes can be merged into master.

v*

These branches contain previous versions, e.g. v4 holds release 4.5, which is the latest release of version 4. These branches can be used for study, historic reference and support, but are not part of the development or release process.