Jürgen Spitzmüller wrote:
Andre Poenitz wrote:
The important part is that once the basic design is accepted, it is
accepted. Period. If you keep quiet, your opinion will be ignored
later. Also, I will respond only to sensible criticisms and
suggestions, not to personal insults.
I think I understand your feelings, but I'd like to note that you are
not setting the rules here. There never was a policy of "if it's in
is it in". Stuff that's in might go out again. Or not. Or whatever.

I will probably not participate the actual discussion on embedding, but being currently responsible for one part of development, I have to make clear that I don't take such claims serious whatsoever.

If a feature shows to be problematic sometime in the future, it is subject to being reverted. No matter who developped it or how much effort it was. Especially if security issues or a pandora's box of bugs is detected.
+1
Who ever will be responsible for the stable 1.6.x series will have to rely on a certain stability of the code. I for one would not want to apply for the job of a stable release manager of 1.6.x if I would not trust the code of 1.6 at least in general areas.
We (I think I can speak for everybody) certainly want you to be the 1.6.x stable release manager. You made a pretty good job at managing 1.5.x.

Abdel.


Reply via email to