or 1.5 since 1.4 is just generics+1.3 -igor
On 4/14/07, Juergen Donnerstag <[EMAIL PROTECTED]> wrote:
I'm not aware of any 1.3 issue it would solve. I'd leave it for 1.4 Juergen On 4/14/07, Eelco Hillenius <[EMAIL PROTECTED]> wrote: > Ok. If it solves concrete problems, we should aim for 1.3. If it > doesn't we should put it to very long term and give priority to the > rest of the back porting 100+ issues to are open in JIRA right now. > > Eelco > > > On 4/14/07, Juergen Donnerstag <[EMAIL PROTECTED]> wrote: > > I'm only saying the approach I took in 2.0 doesn't feel perfectly > > right. Hence it probably wouldn't be a backport but a new > > implementation for 1.x, which will take even longer. I am convinced > > that the MarkupFragment concept itself is the right way to go. > > > > Juergen > > > > On 4/14/07, Eelco Hillenius <[EMAIL PROTECTED]> wrote: > > > > markupfragment is a pretty extensive refactor, and i dont think it will be a > > > > straight backport. i think best is to leave it for 1.4 > > > > > > Then I suggest to drop it altogether. We have enough on our plates > > > right now, and the idea was to have the 1.3 and 1.4 releases as close > > > together as possible. And if Juergen isn't convinced it's for the > > > better in the first place, we should just forget about it. > > > > > > Eelco > > > > > >
