[Angstrom-devel] Opie in Angstrom

[Paul Eggleton]

Hi Paul, thanks for responding.

On Wed, 02 Jan 2008, you wrote:
> > 1) At the moment one has to source
> > conf/distro/include/preferred-opie-versions-1.2.3.inc in local.conf. The
> > autobuilder of course does not allow for this, so this would have to be
> > added to angstrom-XXXX.conf or somewhere else more appropriate. Comments?
>
>   Yes, I guess such patch can be RFCed to be applied to .dev and later
> backported to stable.

OK, I will see if I can come up with a patch for this.

> > http://bugs.openembedded.org/show_bug.cgi?id=3154
>
>   Committed.

Thanks.

> > http://bugs.openembedded.org/show_bug.cgi?id=2875
>
>   I guess it's not the case when something should be done about
> QPEApplication::qpeDir(), right? Will commit later.

With the changes made to the path structure, QPEApplication::qpeDir() is not 
much use in the context it was previously used for, since there is no longer 
a path under which all other Opie files are stored. We could set it to 
return "/usr/" which would be correct for this instance, but would probably 
be wrong for other cases.

> > Would now be an appropriate time for me to apply to become an Opie
> > maintainer in OE?
>
>   We already discussed this I believe - any "today" is better than
> "tomorrow" IMHO ;-). I remember you sent the key already? Can you
> login? If no, please ping coreteam list.

Apparently I can't log in yet, so I have sent a message to the coreteam list 
(I did not get a bounce back this time, is that expected?) However what I was 
mostly referring to was applying for write access to OE for the purpose of 
updating Opie packages in .dev. On the other hand, if there is someone around 
who has the time and inclination to review patches I submit via the 
bugtracker then I don't need this.

>   Otherwise, I'd like to invite to take release management
> responsibilities for this and make a plan. I'd be glad to help, but
> holidays are being, I'm soon will be out of this hyperactivity period
> (as usual, I'm trying to do as much as possible when I can, well
> anticipating that such time won't last long), and I don't feel like lead
> on this. 

OK, so it shall be, then :) I suggest the following plan:

 1) Determine the devices we are initially going to produce images for. h2200, 
hx4700, possibly h3900 are given. Those interested in other devices, please 
speak up now :)

 2) Fix #2875 and any other known showstoppers in the Opie core - I am not 
aware of any others at the moment. If we are to be building from stable then 
#2875, #3154 and any others will have to be RFC'd for merging into stable and 
approved as well.

 3) Build and upload images for those devices. I can do a fair amount of this 
assuming my SSH key gets activated.

 4) Make an announcement about testing, inviting interested parties to test.

 5) Allow for a period of testing (say 2-4 weeks?). New images may possibly be 
uploaded during this time if showstopping bugs are found.

 6) Once the testing period is over, review status and decide on further 
actions.

> For a week or so I'll still be around with good inet 
> connection, and can help with image building/uploading (I don't think
> it's practical/realistical to use Angstrom autobuild server for this).

Fair enough. I don't mind which method we use, whatever works best :)

BTW at some point we will have to determine what to do about the Opie 1.2.4 
release. This list is not really the place for such a discussion so I will be 
posting to opie-devel about it soon, but it is likely that it will be 
dependent on what happens in Angstrom. (In any case I propose we postpone 
1.2.4 until after we have made an Angstrom release containing 1.2.3.)

Cheers,
Paul