Sounds great to me. The fixing of the unique framework bug alone
would make me more than happy. That, together with the hope, that
we'll get a reasonable classpath management within the near future
sounds almost like paradise.
For me personally, it would already be enough, if the classpath
handling would be rolled back to the one until build 4606 (with all
of its quirks).
Timo
Am 12.02.2008 um 05:56 schrieb Mike Schrag:
> Proposal:
> * Fix these handful of regressions that showed up in 3.3 (listed
> above)
> * 3.3.2 is supposed to be out by the end of Feb, at which point we
> declare the unstable branch "stable"
> * Once we are declare stable on 3.3.2, I will modify my original
> classpath management code to use the CURRENT ant build system but
> with the NEW eclipse classpath management (= ant.* stays around,
> but management is much nicer and more fine-grain within Eclipse)
> and I'll commit that
> * After the inside-eclipse classpath system is tested and approved,
> that will move to the "stable"
> * After that moves to stable, the new ant build changes will go in
> * After the new ant build changes are stabilized, it will go to
> "stable"
> * After that, possibly a bug bash? Vote for your most hated bugs,
> etc. I'd also really like to clean up the "zero state" of WO
> development -- smoothing the process for people just starting with
> WO development (I think this ultimately will help everyone by
> tightening the UI) -- if you have specific ideas for this, log them.
> * Back to new stuff?
This archive was generated by hypermail 2.0.0 : Tue Feb 12 2008 - 05:26:29 EST