why? that one can be simple disabled. PageStore works perfectly without it. I think our in/output will always jump into cases that are not completely supported If that is the case. Then use the default one.
Converters didn't cost me time (it was a patch) johan On 3/7/07, Igor Vaynberg <[EMAIL PROTECTED]> wrote:
and how many users did you make unhappy with the half working pagestore? maybe that shouldve been fixed before more energy was spent on backporting the converters. -igor On 3/7/07, Eelco Hillenius <[EMAIL PROTECTED]> wrote: > > We have a team of over ten people, so I don't see why backporting > features can't be done, especially as some are without a doubt worth > it. Take the converter backport. We made at least two users happy > already! And it makes no difference AT ALL to the speed at which the > release comes. The release isn't bound to testing anyway, as the first > goal of the upcoming release is to have a dry run for an Apache ok-ed > release. > > Eelco > > > On 3/7/07, Igor Vaynberg <[EMAIL PROTECTED]> wrote: > > oh please. the more stuff you add the more we have to test, the longer > it > > takes. johan is talking about backporting the models and thats great, > but he > > still hasnt fixed the serialization issues in the pagestore. we needed a > > feature freeze a long time ago, so that we _would_ concentrate on > getting > > the legal issues resolved, but instead weve been happily hacking away. > we > > should at least try to work on some bugs before adding new stuff in. > > > > -igor > > > > > > On 3/7/07, Eelco Hillenius <[EMAIL PROTECTED]> wrote: > > > > > > > thats not the point! its not about api breaks. this is why 1.3 is > taking > > > > forever, you keep adding and adding and adding. > > > > > > What are you talking about? 1.3's release wasn't/ isn't postponed a > > > single day because of us adding new features. The opposite is true: > > > new features (like the converter change) are added because the release > > > isn't out yet and it's still ok to add (or backport) features. > > > > > > No, there is no 1.3 release yet for two (and only two) reasons: > > > 1) legal issues due to incubating > > > 2) setting up the new release process and being short in time for some > > > members who are working on that > > > > > > Eelco > > > > > >
