
What is our policy regarding bugfixes for 1.34.1? For example, I know of a couple of bugs in build system -- one that makes it impossible to build 1.34.1 on cygwin, and another is that "define=FOO" on command line does not work. First was fixed even before 1.34.1, but not included in release, second was just fixed. Now, it's being a month since 1.34.1, and it does not seem like 1.35 is going to be released very soon, so how do we most conveniently provide such fixes to users? Having to manually grab those from trunk is not very nice. - Volodya

Vladimir Prus wrote:
What is our policy regarding bugfixes for 1.34.1? For example, I know of a couple of bugs in build system -- one that makes it impossible to build 1.34.1 on cygwin, and another is that "define=FOO" on command line does not work. First was fixed even before 1.34.1, but not included in release, second was just fixed.
Now, it's being a month since 1.34.1, and it does not seem like 1.35 is going to be released very soon, so how do we most conveniently provide such fixes to users? Having to manually grab those from trunk is not very nice.
Well I hope 1.35 doesn't get delayed too much, but what I've done in the past is issue a library-specific "hot fix": either place it in the vault, or in the usual sourceforge release system. HTH, John.

John Maddock wrote:
Well I hope 1.35 doesn't get delayed too much,
But before one can talk about delay one has to have some idea of an ETA. And, time-frame apart, an idea of a feature set that will be included. None of that I have found any information about. Am I missing something ? Thanks, Stefan -- ...ich hab' noch einen Koffer in Berlin...
participants (3)
-
John Maddock
-
Stefan Seefeld
-
Vladimir Prus