On 24 September 2010 13:12, Thomas Zimmermann <[email protected]> wrote: > I think that the way, to make an shr-t, we used till won't work. For a real > stable shr-t we have to fork the shr-apps and fso. > Because these are under constant developement and introduce new bugs all the > time. That way we can't get a bug free version...
I agree that Ubuntu/Debian model of unstable->testing->stable is the correct one, and I have said so in the past. The answer was always that there was not enough man-power in the project to handle it, which given the current state of SHR-T, seems true. For me, an answer would be to move SHR wholesale to Debian. The build environment and bug tracker is all set up. There is a pkg-fso repository for those packages like e17 which are already in Debian but whose Debian maintainers don't want to stay as bleeding edge as SHR. The package migration unstable->testing->stable is then automatic, provided no serious bugs are reported. Regards Jeff _______________________________________________ Shr-User mailing list [email protected] http://lists.shr-project.org/mailman/listinfo/shr-user
