Hello Henning, I believe the right approach is to put the local_route into defines and disable it by default. If someone wants to use it, then he/she must be aware of the risks, enable the compile flag and install from sources. I don't like to have a major release with such many issues enabled by default. People can maintain own trees with local route on if they wish to do so. I personally don't use private trees and rely only on public SVN.
Cheers, Daniel On 06/18/08 19:18, Henning Westerholt wrote: > On Thursday 12 June 2008, Henning Westerholt wrote: > >> [..] >> > > Hi, > > i just like to reply to myself to add some informations for the archives - > don't want to start another flamewar.. ;-) > > Daniel, Bogdan and i discussed this off-list in the last week. > > First of all its safe to just not use this new features, then now (new) bugs > should be show up. If there are issues, then we'll fix them, as usual. If > somebody really want to be on the safe side, he/ she should just add some > #ifdefs around this feature in their own tree (rev 4317). Design issues and > better integration can be addressed in the next major release. > > I hope we learned something of this conflict. Lets create some policies that > something like this hopefully didn't happen again. > > With best regards, > > Henning > > _______________________________________________ > Devel mailing list > Devel@lists.openser.org > http://lists.openser.org/cgi-bin/mailman/listinfo/devel > -- http://www.asipto.com _______________________________________________ Devel mailing list Devel@lists.openser.org http://lists.openser.org/cgi-bin/mailman/listinfo/devel
