Re: OPIE 1.2.3 release?

On Wed, Jan 24, 2007 at 12:00:03AM +0200, Paul Sokolovsky wrote:
> > Considering that except for Paul E's fixes the rest are one liners to
> > deal with minor annoyances in often dusty corner cases I think a point
> > release is not that hard to come up with. And I would like to see a
> > point release soon just to capture that stuff.
> 
> > I don't think that a point release now is a big deal. It just sets us up
> > for another one in a few months.
> 
>   And that's exactly a concern - too hasty a release now, with some
> things omitted, and then long wait for next chance to add them.

Sure, I can see that concern. I am on board at least until I get to the
bottom of pile of patches which should be enough for at least two
releases. But I can see how that is not much of a comfort.

So let's try to meet in the middle. Say three weeks from now or
2007-02-12 for the freeze.

>   I myself first of all concerned with machine support in OPIE -
> there're few patches fly around adding this or that machine, or BT
> support, or something like, and it would be nice to collect them. And
> actually, it may be just good idea to add machine IDs for all ports
> maintained in HH.org CVS, plus maybe some active outside ports.

Well, I agree with you on principle. But in practice I would say that
just having a machine ID should not be support enough to have an Opie
ID. I say that if a machine has stable framebuffer, input and
flash/storage support at least it can be tracked in Opie.

But please submit patches and we can sort this out.

>   And, about release procedure - I wanted to write separate RFC, but
> just can't find enough time now. So, quick brain-dump: what about
> making subreleases for individual OPIE apps, if they undergo some
> useful changes. Such subreleases might use 4th version component, like
> libopie2-1.2.2.1. Having such releases would help distros to ship
> updated OPIE applications sooner (without risk of using "unstable"
> stuff), and that would be helpful, unless there's going to be short
> cycles for main releases, which we probably shouldn't count for.

I think with very little development being done on individual apps there
is little or no reason to have them be further versioned. At the least I
won't bother tagging or branching for individual apps except for
extremely large apps and only if there is another developer to support
them. At this point of Opie's development I just don't see the need to
break out apps at all and only see trouble.

So to sum up. I will definitely agree to a later freeze. I propose
2007-02-12. If everyone agrees I will update the page that Dan started:
http://opie.handhelds.org/cgi-bin/moin.cgi/Opie123ReleasePlan

E

-- 
Erik Hovland
mail: erik AT hovland DOT org
web: http://hovland.org/
PGP/GPG public key available on request
_______________________________________________

http://opie.handhelds.org/cgi-bin/moin.cgi/DeveloperWikiIndex

Opie-devel mailing list
[email protected]
https://handhelds.org/mailman/listinfo/opie-devel