Douglas Gregor wrote:

We're going to need to roll a 1.34.1 release in the very near future; I suspect we'll wait until 1.34.1 is out the door before moving to Subversion.

Might it be a good idea to set a hard timeframe for this upfront, before things to start slipping again ? Also, is there a list of regressions / bugs that are to be addressed in this ? Thanks, Stefan -- ...ich hab' noch einen Koffer in Berlin...

Thomas Witt wrote:

...

Also, is there a list of regressions / bugs that are to be addressed in this ?

Are you volunteering to compile that list from the messages on devel?

I'm afraid I don't understand the issues well enough. I have read about some issues with iostreams (though I'm neither sure about what that means in detail, nor what risk fixing that may involve), and noticed some mention of one or two other (minor) things that need fixing. All I'm saying is that it may be best to specify the bugs that need fixes, and refuse *all* other checkins, or else things will get out of hand again. (I for one have checked in a small backport this morning to boost.python, assuming the 1_34 branch was now being prepared for 1.35, as discussed by Doug et al. some weeks ago.) Regards, Stefan -- ...ich hab' noch einen Koffer in Berlin...

Thomas Witt wrote:

...

(I for one have checked in a small backport this morning to boost.python, assuming the 1_34 branch was now being prepared for 1.35, as discussed by Doug et al. some weeks ago.)

And this was a bad idea. RC_1_34_0 is frozen and will only be open to bug fixes that are approved.

I understand that, now. Until this morning it sounded as if 1_34 would become the new 1_35, and there was no plan for a bug-fix release. Regards, Stefan -- ...ich hab' noch einen Koffer in Berlin...