[maemo-developers] Application in Extras-Devel OK? Promote it!

[From: Ed Bartosh]

On Wed, 2008-07-02 at 16:33 +0200, ext Niels Breet wrote:
> Now that we have the autobuilder[1] in place for Diablo, it is a good time
> to talk about how to get your package from Extras-Devel into the Maemo
> Extras repository.
> 
> Before a package will end up in Extras and is installable for end-users on
> their device, it will go through a few steps:
> 1. source package uploaded to autobuilder incoming queue\
> 2. autobuilder builds package and moves it into the incoming queue from
> Extras-Devel
> 3. queuemanager for Extras-Devel will put the package in the Extras-Devel
> repository
> 4. developer checks packages from Extras-Devel and if the package is OK:
I think, this 'OK' needs to be clarified, I think.
>From my point of view it means that package is ready for enduser usage,
installable on the tablet, tested by developer or, better, testers. The
fact that package is buildable is not enough to promote it to extras.

I'm using extras-devel for all my maemo packages and sometimes I keep
packages in extras-devel for a long time. Just because I think they're
not ready for enduser or not enough tested yet. 

The typical workflow for packages should be somethink like this, IMHO:
1. Upload alfa/beta quality packages to autobuilder queue
2. Fix failed builds if any
3. If packages build successfully and appear in extras-devel - Install
them on tablets and test.
4. If any bugs found - fix them and goto 1.
5. If no bugs found during testing and developer thinks that packages
are ready for enduser usage - promote them to extras. 

> 5.promote the package to Extras using the Promoter.


Regards,
---
Ed