Big picture about Plasma Active on MeeGo

[Maurice de la Ferte]

Hi all,

I like to clarify a bit about our MeeGo project and image structure.
The following lines do not define anything they should just show
how do we work on top of MeeGo at the moment and what is the idea behind.

The MeeGo Open Build Service 'Devel' Project
--------------------------------------------

This is the place where the integration of Plasma Active Contour on MeeGo
happens. This means in a short term, many updates a day, broken builds,
experimental work, automatically updated packages by continuous integration.
No place for end-users and testing by quality assurance. But developer will
get feedback by there own changes so soon as possible by using the related
image and 'zypper up'.

Alias: 'Project:KDE:Devel', 'meego devel project'
URL: https://build.pub.meego.com/project/show?project=Project%3AKDE%3ADevel
Stability: low
User: developer, integrators
Update/Change Interval: very often
Related Image: http://share.basyskom.com/contour/Deployment/latest-meego-plasma-contour-in-progress.html
Image Update Interval: Rarely - no hints about on mailing lists.


The MeeGo Open Build Service 'Testing' Project
----------------------------------------------

This is the staging project of Plasma Active Contour on MeeGo. This means we take
this project to create a kind of dry run (staging) image releases. In this project
no direct development will happen, all changes get in via Open Build Service
'submit requests'.
Those images will be tested and feedback will given to the developers e.g. by bug
reports and or via IRC. Those staging images gives a good overview about the actual state
of Plasma Active Contour on MeeGo. But it is strictly recommended to install every time
a new clean image to a device. This keeps sure that everyone who is involved is testing
and talking about the same collection/versions of software. By this we try to keep sure
to prevent bad side effects by e.g. custom configurations and time of the last update.
If there is agreement about improvements or bug fixes can be confirmed all or separate
parts will shipped into the 'Stable' project.

Alias: 'Project:KDE:Trunk:Testing', 'testing project', 'staging project'
URL: https://build.pub.meego.com/project/show?project=Project%3AKDE%3ATrunk%3ATesting
Stability: middle
User: integrators, quality assurance, many kinds of contributors
Update/Change Interval: often
Related Image: http://share.basyskom.com/contour/Deployment/latest-meego-plasma-active-testing.html
Image Update Interval: often - automatically info on active at kde.org

The MeeGo Open Build Service 'Stable' Project
----------------------------------------------

This is stable project of Plasma Active Contour on MeeGo. This means we are creating
releases and demos on this base. In this project no direct development will happen,
all changes get in via Open Build Service 'submit requests' from 'Testing' project.
An device which is deployed with an 'Stable' release image can and should be updated.
We hope to get end-user feedback about usability in practice, long term behaviour and
bugs.

Alias: 'Project:KDE:Trunk', 'stable project'
URL: https://build.pub.meego.com/project/show?project=Project%3AKDE%3ATrunk
Stability: high
User: end-user
Update/Change Interval: often, but less often as the 'Testing'
Related Image: http://share.basyskom.com/contour/Deployment/latest-meego-plasma-active-stable.html
Image Update Interval: rarely, trigger by a reason - automatically info on active at kde.org


I hope this info is useful and do not cause more confusion ;)

Cheers

Maurice