[maemo-developers] PR1.2 SDK for Extras-devel: how to solve?

From: Ram Kurvakat rkmaemo at gmx.com
Date: Wed Apr 7 21:33:44 EEST 2010
I would like to throw in my 2 pence as well for what its worth.

The idea is to give a choice to the developer to choose which SDK the autobuilder needs to use and to which repo the app needs to go to.
Providing an option in the debian control file to build against the user specified SDK since the developer knows what SDK he/she uses.

Xsbc-sdk : PR1.2

Also, we can maintain n and n-1 version of the repository at any time to limit the number of maemo OS trunks.

does it look feasible ?

> ----- Original Message -----
> From: Andrew Flegg
> Sent: 04/07/10 03:41 PM
> To: Bryan Jacobs
> Subject: Re: PR1.2 SDK for Extras-devel: how to solve?
On Wed, Apr 7, 2010 at 15:13, Bryan Jacobs <no at landwarsin.asia> wrote:
> It seems to me that the real problem is actually the difficulty in
> implementing #4 above. If there were magically separate infrastructure
> for each incompatible release, there would be no issue - a developer
> uploads their package to each repository for which it builds
> (preferably through a list of checkboxes in the web interface), and
> a user selects one or more package sources that match the preinstalled
> software on their device. No problems, mate.

True; however what about the QA process? The UI at
http://maemo.org/packages/ is getting better, but it's also getting
more familiar. How do we:

 a) not confuse ad-hoc testers
 b) ensure that versions in all repos get tested?

One suggestion would be to promote all versions simultaneously, but
there are obvious drawbacks with that!

> So the real issue is that creating a new branch requires a nontrivial
> amount of work. This is a computerized system; computers excel at
> automation. Why not spend the one-off time to allow for near-instant
> creation of a new branch? Once that's done, future releases will just
> consist of "oh, I should create a new repository for this release. Let
> me run that script again with a new name and then upload the new SDK
> release to it".


> Have I missed some important consideration?

I think the issues aren't technical (although streamlining the repo
creation is obviously part of it), but more procedural. I could be
wrong. I wonder what the testing squad think (I'll poke VDVsx).



Andrew Flegg -- mailto:andrew at bleb.org | http://www.bleb.org/
Maemo Community Council chair
maemo-developers mailing list
maemo-developers at maemo.org
More information about the maemo-developers mailing list