On Sat, Feb 08, 2014 at 10:49:05AM +0100, Jake wrote: > 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.
I agree with everything Jake said, if there are "stabilization" patches going in, I'm OK with keeping it on the same OE release for longer, but without more people contributing fixes to "stable" branch it doesn't make much sense to keep it open forever. We're no longer tracking upstream very closely, we upgrade only to stable releases which happen twice a year. There are still "dylan" branches for all layers we're using, so if someone wants to spend time on shr-image as it was in staging feed 125 (last one based on "dylan" before upgrading to "dora") it's still possible and easy to do, just download SHR Makefile from right branch. I would recommend to stay with newer OE, because there are more bugfixes still going in, it supports building on newer distributions, contains newer components and in general SHR will look more alive if we're using less then year old components. dylan: http://build.shr-project.org/shr-2013.07/dylan/ dora: http://build.shr-project.org/shr-2013.07/ You can see that they are almost the same feature/bug wise. > > 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. It would work better if we have more users and devs actually testing those staging images. The staging feeds 125 - 134 are basically "frozen" and contain only bug fixes. The only significant upgrade was gta04 kernel, requested by couple people. -- Martin 'JaMa' Jansa jabber: martin.ja...@gmail.com
signature.asc
Description: Digital signature
_______________________________________________ Shr-devel mailing list Shr-devel@lists.shr-project.org http://lists.shr-project.org/mailman/listinfo/shr-devel
