Re: muesli's repository strategy + packages are getting updated

>KDE_CVS_HEAD: latest avail. cvs packages from the head branch. pretty much 
>what you used to get from orth's repository. THIS IS INTENDED FOR 
>DEVELOPERS / HARDCORE USERS in the future.
>
>KDE_DEV_RELEASE: latest released development version. this would be stuff like 
>"rc1", "beta2". in times with less officially tagged releases, we will 
>declare our own package sets as dev_releases, if we trust them and they feel 
>stable enough. these package sets will come straight out of the KDE_CVS_HEAD 
>repository. THIS IS INTENDED TO BE THE NEW SOURCE FOR "NORMAL" USERS in the 
>future.
>
>KDE_STABLE: this will be the first repository, which i will set up after the 
>current compile process (mentioned at top of mail) is complete. it is kind of 
>redundant, since this package set will be equal to the official debian set. 
>but since i'll provide the newest stable release way before debian, it is 
>there and will stay there... till the next release.
>
>  
>
This almost sounds to good to be true! I would love to have such an 
service, if the latest cvs binaries is buggy, I'll just use the 3.2 
stable repository. NICE!

/David