actually in part your concerns were right (but they don't affect lmde anymore because since the introduction of the update-packs we have ways of controlling that influx)
last time (fev 2011 viewtopic.php?f=201&t=65740&start=0
) still with the original lmde setup (tracking directly testing) the end of the deep-freeze was interesting
because then there's a backlog of development that hits the newly created testing.
during this deep-freeze sid slows down (mainly because the debian devs are focused in releasing stable in the best shape possible) but doesn't stop and a couple weeks after the freeze is over there's an huge update in testing.
this time lmde will be safe from that: the UP will create a buffer giving the users stability.
I agree with almost all of this.
The only thing that I can say is not completely correct is when the deluge of packages hits the "testing" repo.
I installed Squeeze when it was testing. Was planning on using it as my production OS. Feel in love with testing. Changed my sources.list from reading "squeeze" to "testing".
The very day tbat Squeez went "stable" I had over 1000 packages to be upgraded in testing. There really was no pause at all before that happened. Was kind of a shock as you may imagine.
At least in my case there was no problem with that huge update/upgrade cycle.
I think the average user, used to "stable" releases, is going to be a lot happier with LMDE.
The LMDE repo maintainers are probably in for a very busy time though. I am sure that they will do a supper job of it too.
Dell XPS 420 Core2 Quad Q 6600, audigy5.1, Radeon HD 6450 - currently 4 320Gb HDD, Debian Squeeze for secure use, Debian testing for daily use, Debian Sid for fun.