HI!
Are there any plans when to release 2.4.9? I vaguely remember some interesting fixes and noticed that some things were already back-ported to RE24.
Ciao, Michael.
--On Friday, April 04, 2008 5:51 PM +0200 Michael Ströder michael@stroeder.com wrote:
HI!
Are there any plans when to release 2.4.9? I vaguely remember some interesting fixes and noticed that some things were already back-ported to RE24.
I don't see a particular point to it until such a time as the numerous ITS' around replication are resolved. Just my 2c. ;)
--Quanah
--
Quanah Gibson-Mount Principal Software Engineer Zimbra, Inc -------------------- Zimbra :: the leader in open source messaging and collaboration
Quanah Gibson-Mount wrote:
--On Friday, April 04, 2008 5:51 PM +0200 Michael Ströder michael@stroeder.com wrote:
HI!
Are there any plans when to release 2.4.9? I vaguely remember some interesting fixes and noticed that some things were already back-ported to RE24.
I don't see a particular point to it until such a time as the numerous ITS' around replication are resolved. Just my 2c. ;)
Seems to me that we're just about there now. The only other issue I'd like to close out is 5383, assigning a public OID to the config schema.
Howard Chu writes:
Seems to me that we're just about there now. The only other issue I'd like to close out is 5383, assigning a public OID to the config schema.
Do anyone have opinions about my questions in ITS#5408, back-ldif bugs? In particular, how much and when should be rename the LDIF files? (back-ldif is broken if it gets used as a regular backend so it gets filenames with escape characters and the like.) If we rename files in 2.4 instead of punting to 2.5, it would be better if it happens early.
Hallvard B Furuseth wrote:
Howard Chu writes:
Seems to me that we're just about there now. The only other issue I'd like to close out is 5383, assigning a public OID to the config schema.
Do anyone have opinions about my questions in ITS#5408, back-ldif bugs? In particular, how much and when should be rename the LDIF files? (back-ldif is broken if it gets used as a regular backend so it gets filenames with escape characters and the like.) If we rename files in 2.4 instead of punting to 2.5, it would be better if it happens early.
Fair enough. Do it now. We ought to be getting 2.4 stable within the next release or two.
back-ldif was never promoted as a general purpose backend, so I wouldn't worry too much about backward compatibility. Just publish a note to slapcat old DBs and reload them in this release.
Howard Chu writes:
Hallvard B Furuseth wrote:
Do anyone have opinions about my questions in ITS#5408, back-ldif bugs? (...)
Fair enough. Do it now.
Well, this weekend I guess. But I need advice about Windows filenames, at least. No point in renaming files from one broken naming scheme to another broken one. And whether to use a common naming scheme for Unix and Windows, or OS-specific schemes.
I need advice or "yes/no" about the other functionality issues listed too, but they can wait till someone has time to look at them. Except referrals, that code is too broken to keep:-)
I wrote:
Howard Chu writes:
Hallvard B Furuseth wrote:
Do anyone have opinions about my questions in ITS#5408, back-ldif bugs? (...)
Fair enough. Do it now.
Well, this weekend I guess.
...well, almost. I've finally tested and committed to HEAD the filename changes, at least. (As stand-alone changes.) Not tested on Windows, though I did #define various macros with crazy values to "emulate" it a bit.
--On Wednesday, April 16, 2008 12:15 AM +0200 Hallvard B Furuseth h.b.furuseth@usit.uio.no wrote:
I wrote:
Howard Chu writes:
Hallvard B Furuseth wrote:
Do anyone have opinions about my questions in ITS#5408, back-ldif bugs? (...)
Fair enough. Do it now.
Well, this weekend I guess.
...well, almost. I've finally tested and committed to HEAD the filename changes, at least. (As stand-alone changes.) Not tested on Windows, though I did #define various macros with crazy values to "emulate" it a bit.
Okay. So do we want this in for 2.4.9?
--Quanah
--
Quanah Gibson-Mount Principal Software Engineer Zimbra, Inc -------------------- Zimbra :: the leader in open source messaging and collaboration
Quanah Gibson-Mount writes:
h.b.furuseth@usit.uio.no wrote:
Okay. So do we want this in for 2.4.9?
Since it's an incompatible change I'd rather see it early in the release cycle. Even if the incompatibility is unlikely to hit many users. Provided someone *tests* it on Windows, using back-ldif as a primary backend with illegal filename characters in the DNs. I can't.
Michael Ströder wrote:
Howard Chu wrote:
The only other issue I'd like to close out is 5383, assigning a public OID to the config schema.
I'd really appreciate it. :-)
Already done in HEAD...
Howard Chu wrote:
Quanah Gibson-Mount wrote:
--On Friday, April 04, 2008 5:51 PM +0200 Michael Ströder michael@stroeder.com wrote:
HI!
Are there any plans when to release 2.4.9? I vaguely remember some interesting fixes and noticed that some things were already back-ported to RE24.
I don't see a particular point to it until such a time as the numerous ITS' around replication are resolved. Just my 2c. ;)
Seems to me that we're just about there now. The only other issue I'd like to close out is 5383, assigning a public OID to the config schema.
I've rolled all of the syncrepl/syncprov updates into RE24. There's still plenty of fixed ITS's that need to be merged.
--On Friday, April 11, 2008 4:11 AM -0700 Howard Chu hyc@symas.com wrote:
Howard Chu wrote:
Quanah Gibson-Mount wrote:
--On Friday, April 04, 2008 5:51 PM +0200 Michael Ströder michael@stroeder.com wrote:
HI!
Are there any plans when to release 2.4.9? I vaguely remember some interesting fixes and noticed that some things were already back-ported to RE24.
I don't see a particular point to it until such a time as the numerous ITS' around replication are resolved. Just my 2c. ;)
Seems to me that we're just about there now. The only other issue I'd like to close out is 5383, assigning a public OID to the config schema.
I've rolled all of the syncrepl/syncprov updates into RE24. There's still plenty of fixed ITS's that need to be merged.
Ok. I'll be able to start work on this next week.
--Quanah
--
Quanah Gibson-Mount Principal Software Engineer Zimbra, Inc -------------------- Zimbra :: the leader in open source messaging and collaboration