Hi all!

After the release of OpenSAF 5.2.0, we will start using the new GIT 
repository for OpenSAF development. You will find a link to the GIT 
repository at the far right of the toolbar at the OpenSAF SourceForge 
page. Or you can directly paste in the following URL in your web browser:

https://sourceforge.net/p/opensaf/code/ci/develop/tree/

At the same time as we switch to GIT, we also introduce a new branching 
and release strategy. This strategy is described in the following document:

https://sourceforge.net/projects/opensaf/files/docs/OpenSAF%20Branching%20and%20Release%20Strategy%20170315.pdf/download

Due to the new naming scheme for releases described in the document 
above, the next OpenSAF feature release is named 5.17.08 (for August 
2017) and is developed on the "develop" branch. The next maintenance 
release is named 5.17.06, which is a patch release on top of OpenSAF 5.2 
and would have been called 5.2.1 in the old naming scheme. OpensSAF 
5.17.06 is developed on the "release" branch in GIT. Please push 
maintenance fixes to both the "develop" branch and the "release" branch, 
in the same way as we used to push maintenance fixes to both 
opensaf-5.x.y and default in Mercurial. Please also push maintenance 
fixes to the "default" branch in Mercurial during a short transition 
period before we completely move to GIT.

There is also a new OpenSAF wiki page describing the basic steps for 
working with GIT to develop OpenSAF:

https://sourceforge.net/p/opensaf/wiki/GIT/

The OpenSAF review script (tools/devel/review/submit-review.sh) has been 
updated to use GIT. It will send out E-mails to the opensaf-devel list 
as usual. In addition, it will also push the ticket branch to your 
personal SourceForge repository. This is for the reviewer's convenience, 
so that he/she can simply pull from SourceForge instead of cutting the 
code from a series of E-mails.

Since all of this is completely new there will probably be some initial 
problems before everything works smoothly. Please try out the new 
repository and review script, and report anything that is unclear or 
isn't working.

regards,

Anders Widell



------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Opensaf-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-devel

Reply via email to