On 2010-04-22, Nicola Mfb wrote: > Bumps introduce new bugs, only backports are a suitable way to manage > a stable release and I think there is no man power nor the will to do > that.
Exactly that is the problem. Well it is a problem of man-power mostly I guess. > Actually *all* is in a developement phase, cornucopia, gui apps, E, > the distro is based on a live OE tree, it's obvious that the > stabilization phase, IMHO, will not start before the next year, not > with actual conditions, and not before developers will be happy of > their work, and will think to maintain a second branch (not only OE, > but apps and framework too) with full backports. Anyway I guess there > is no fun in that, and it's hard to convince all that peoples spreaded > on so different projects, emh... it may never happens :) Hehe, you summed it up quite nicely. There is simply too many moving parts at the moment. Part of that are SHR design choices though, like always going for the latest illume that is obsoleted a year later for another rewrite ;-). If e.g. the SHR phone apps were not so tightly knitted to a EFL-on-the edge where one version of the SHR apps requires a specific version of EFL, it would be easier to just bump the phone apps, for example. I am not advocating GTK (or QT) here, but by building them on a more stable API, updating the phone apps would have been easier for myself. But I guess, it is less fun to code in :-). > In the meanwhile it may be nice to manage a list of old but known to > work rootfs, that may be an easy community task. Yes, but they could well be put on the build.shr-project server so they are available from an "official" location. Sebastian _______________________________________________ Shr-User mailing list [email protected] http://lists.shr-project.org/mailman/listinfo/shr-user
