[prev in list] [next in list] [prev in thread] [next in thread]
List: kde-active
Subject: Workflow and integration
From: Marco Martin <notmart () gmail ! com>
Date: 2012-03-30 12:04:34
Message-ID: 201203301404.35093.notmart () gmail ! com
[Download RAW message or body]
Hi all,
this is a proposal on how to handle the development in a way where is easier
to assure qa and have device specific images.
from a short chat with some people it was seen there was a need of
reorganizing a bit how git branches are kept and how this reflects on obs.
I am explaining it now how i understood it, so please correct if wrong ;)
* Need for a stable, always releasable master
* How to do that? an "integration" branch
* integration is kept always merged, up to date with master
* features are developed in feature only branches
* when a feature is almost ready is merged into integration, people test it,
fixes are done in the feature branch, then re-merged
* when tested enough, it gets merged into master
* Device specific (Archos, vivaldi, whatever) releases are branches of master
called like Device/Vivaldi (only a stable state needed? or integration/stable
for that too?)
This reflects in obs in the following way
* integration project points to integration branch, (or devel can be
repurposed to it)
* testing project points to master: master became a stable branch now
* Each device specific git branch has an own obs project
this is just an idea, please comment ;)
in the end a good final workflow document will need to be in place
Cheers,
Marco Martin
_______________________________________________
Active mailing list
Active@kde.org
https://mail.kde.org/mailman/listinfo/active
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic