On 01/11/10 13:26, Patryk Benderz wrote: >> -Not trying to defend ourselves or anything, but keep in mind that SHR >> is not Debian with>1000 active devs. We derive from a highly unstable >> distribution (OpenEmbedded development tree), and much of that is >> outside our control. So stuff changing and disappearing might not always >> be our fault, we cannot check every change that goes into OpenEmbedded >> and we don't have the rights to veto those that we don't like. > I get your point, but what about deriving from stable branch of OE? Is > it out of consideration?
There is one dead-end stable branch which uses so obsolete stuff that it is out of question, yes. We do need an up-to-date kernel and up-to-date xorg for example as previous releases simply did not have support for the hardware. Also, frankly, I would not be very motivated to do any dev work if I knew that it would be a dead-end that will become stale and can't be used on future versions. >> -3rd, much of our functionality comes from 3rd party apps and we are at >> their whim: eg if mokonnect doesn't work or were not developed anymore, >> there is little the SHR devs can do about it. Similar with our >> technology backend: FSO. Currently there is only 1 guy working (unpaid!) > Who is that? Mickey Lauer > well, take a look at QtMoko. If I am informed well, it is developed by > one guy, Radek Polak. Considering this, it is obvious that QtMoko > progress is slow, but it is quite stable distro. Maybe because it > derives from stable branch? I can't comment on QtMoko, sorry. Never seen it. > My proposition is this: on 14th CU I will put an entry that SHR-testing > is waiting for last bug reports before renaming it to Stable. Maybe this > way we will encourage some additional men-power for testing and bug > reporting. What about that? Sounds good to me. I just cannot promise that upgrades from one stable snapshot to another stable snapshot will always work. But it can be a long lived stable release. _______________________________________________ Shr-devel mailing list [email protected] http://lists.shr-project.org/mailman/listinfo/shr-devel
