Hi Gerhard,
yes, that would be one possible good approach and has also been done in
the past. But this needs a maintainer for that stable version.
Due to general lack of developers/maintainers in this project the
current process was thought up, to have at least a little more stability
than with just an unstable version.
However we even with this setup not very many bugs get fixed (due to
lack of devs).
JaMa is the one who keeps the project alive - I'd say. I think he has an
interest in keeping shr close to openembedded development, as he is an
OE maintainer. That's why anything is happening in this project at all,
though moving along fast.
With that - if anybody got time and wants to maintain a stable/testing
branch, don't hesitate to step up.
Just fixing one or another (long standing) bug would help the cause already.
In conclusion I think there are two ways:
First would be getting more devs who fix bugs and support the whole
stabilizing chain. (Suggestions how to achieve that?)
Second would be moving along like in the past. As Enlightenment got a
lot more stable in the last year there is more (of the already sparse)
dev time available to to other things. So bugs are getting fixed every
now and then.
Cheers
Jake
On 02/08/2014 09:31 AM, Gerhard Rieger wrote:
Hi all,
I'd recommend to generate a stable image by means of feature freeze and
only fixing bugs.
IMHO the actual process of development versions and milestones is not
useful for people like me that are really interested in SHR but need a
starter image that provides basic OS, GUI, and HW support.
What do you think?
Regards
Gerhard
_______________________________________________
Shr-devel mailing list
Shr-devel@lists.shr-project.org
http://lists.shr-project.org/mailman/listinfo/shr-devel
