CVS is NOT something you should bother posting about. Expect it to be buggy, and expect it to be unsupported.

CVS is NOT for productive use. it's a development version that sometimes behaves strange or make problems.

Sorry, but that answer doesn't fly. In an open-source app with multiple developers, you can expect CVS to be buggy, yes, but you should welcome bug reports with open arms. Since your SF bug-reporting is restricted to project admins only, how else does one report bugs?

If you commit to CVS, you'd better be confident that your changes work, and desire notification that they don't work as you expected.

Take a look at what it says on the forum main page right under Bugs

This is for bugs only and for public releases only! Please select another forum for other issues.

There is no forum for CVS issues for a good reason: there is no reason to expect CVS to be a viable product at any given time. By design it is a development tool. May I suggest you send an email or PM to one of the members of the dev team?

Good suggestion; I'll do that. Thanks for pointing out the notice; I missed it :#

the point is: maybe the devs are aware of the problem and working on something else or new features. or it's a sideeffect because they are rewriting some parts and so on.

we don't want to blame you. don't understand as wrong.
we just want to make clear that CVS is only and always "work in progress" and bugs may be included - sometimes intentionally, sometimes not

kiesow wrote:

... and bugs may be included - sometimes intentionally, sometimes not

Hm! Now I know y'all have bugs in there just to keep people like me on the official release! Personally I didn't even get as far as the issue fumanchu identified :(