Difference between revisions of "Plasma/PlasMate/Development"

Line 4: Line 4:
 
* new features must go in a new branch
 
* new features must go in a new branch
 
* The branches plasmate/x.y must contain the relative release code, which will derive from the master branch
 
* The branches plasmate/x.y must contain the relative release code, which will derive from the master branch
** Before the creation of a new plasmate/x.y a git tag must be added to the master branch
+
** Git tags are added for every release, marking the final commit of the released code base
  
 
==Install==
 
==Install==

Revision as of 12:12, 27 August 2012

Development

Git Workflow

  • The master branch must be always ready for release
  • new features must go in a new branch
  • The branches plasmate/x.y must contain the relative release code, which will derive from the master branch
    • Git tags are added for every release, marking the final commit of the released code base

Install

See the plasmate/PACKAGERS file

Source Code

projects.kde.org [1]

TODO


This page was last edited on 27 August 2012, at 12:12. Content is available under Creative Commons License SA 4.0 unless otherwise noted.