Hi, my opinion is that we should be using rolling release for shr-unstable, as there's lots of changes each day. Then, use snapshots of this release to create shr-testing images which would finally end into shr-stable images. As you can see, this way is similar to what we are doing nowadays.
I think that the problem is not this way, but the lack of documentation on what's happening. There's a lack of communitaction between users and developers, and we should try to improve this. The same happens between community<->people out of the community, as it's really difficult to know what things are being done. From a newcomer, it's even difficult to know if the distro is alive! I have already started to work on this. For those who don't know about it, throughout the last weeks I've been writting some blog entries in the official shr blog (http://blog.shr-project.org) speaking about which things we fix, which things we improve, etc. -- Pau Espin Pedrol mail/jabber: [email protected] http://blog.espeweb.net
_______________________________________________ Shr-devel mailing list [email protected] http://lists.shr-project.org/mailman/listinfo/shr-devel
