IMHO as a S2 user (or any other API user): When something breaks backward compatibility, I as a user expect to detect the change as early as possible, which in the ideal case would be when recompile the project.
In this case, if the hypothesis is that people have a hard time reading the docs (which I think is quite good), then there is a high probability that this change will pass undetected to production applications (because you need good testing in place to detect the change in the defaults). Being said that, if the current default is nobody default, then promote the attribute as "required". Disadvantages: 1) Everybody are forced to add it. 2) It breaks pages (because of the change in the TLD). Advantages: 1) Can be detected earlier than changing the default only. 2008/9/6 Dave Newton <[EMAIL PROTECTED]>: > --- On Sat, 9/6/08, Musachy Barroso wrote: >> I think it is a more appropriate default value. +1 (it >> breaks compatibility tho) > > Not as bad as the EL thing ;) > > How are release notes created? Is it just a wiki page? I'll add it to that > and update the relevant wiki docs. > > Dave > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
