muesli's repository strategy + packages are getting updated

hey guys!

good news first: yes, new packages are on their way. yes, it is 3.2.0_RELEASE.

as "announced" yesterday, i will explain you the strategy of my repository in 
some other mail. uhm, this is this mail. :-)

life on bleeding/cutting edge is hard. well, this might be no news to you, a 
user of cvs-compiled software for quite some time probably. but last 
autumn/winter really hit me hard, when proper development was quite 
impossible, since konqueror crashed every other click, memory leaks were here 
and there and you couldn't even trust konsole's stability.

this was the point where i started thinking about how to get rid of these 
situations and still offer fresh cvs packages. the result is this little 
scheme, which is basically split in three _different_ repositories:

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.

users got plenty of options now:

1. always use the already-approved KDE_DEV_RELEASE which should be a nice 
compromise between stability and new features.

2. a mixture between KDE_DEV_RELEASE and KDE_CVS_HEAD with manually selected 
packages.

3. developing, feature preview and bug-fixing with KDE_CVS_HEAD.

4. if everything fails, get back to KDE_STABLE.

let me know what you think about it...

muesli
http://blog.chris.de