Your patch -- your decisions :) Backward compatibility can be a relative term. The idea of having a patch is that people can try it with their own applications and say whether it works for them.
We are deprecating, replacing, and removing features in the 1.x series. We just have to do things step by step, release by release. A patch (or extension) can tell us where people want to go, so we know what to deprecate now, so that we can remove it later. -Ted. On Fri, 11 Mar 2005 16:18:34 -0800, Dakota Jack <[EMAIL PROTECTED]> wrote: > "Okay!", he said, pulling up his britches with gnarled thumbs. I am > going to submit a patch for Struts upload to v1.3 if I can get the > committers to tell me what this patch must do. I assume that it must > be backward compatible and that is it. Any other requirements? > > Jack > > -- > "You can lead a horse to water but you cannot make it float on its back." > ~Dakota Jack~ > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- HTH, Ted. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
