Hi, Torsten Curdt did say that he wanted to check out ASM a little first before casting his vote. He's away on holiday at the moment, but due back shortly. As there's no big rush on this, I suggest we hold off until Torsten has had a chance to make up his mind. When Torsten returns would also be a good time to notify the user list of this, and give them a chance to discuss it too (though of course if they just say "we want BCEL fixed, though we're not going to do anything about it" then too bad :-).
Regards, Simon On Sat, 2005-05-28 at 15:42 -0400, Dave Brosius wrote: > I'm +1 to suggest asm for new projects. > > A decision should be made as to what still-open bugs should be included for > a bug fix release. > > > ----- Original Message ----- > From: "Henri Yandell" <[EMAIL PROTECTED]> > To: "BCEL Developers List" <bcel-dev@jakarta.apache.org>; > <[EMAIL PROTECTED]> > Sent: Friday, May 27, 2005 11:05 PM > Subject: Re: proposal to post deprecation notice on BCEL webpage > > > I'm +1 to: > > 1) Provide a link to ASM on the site with explanation that we > recommend ASM for most people considering using BCEL for the first > time. > 2) That we release a bugfix version of BCEL as soon as the bugs are > fixed. I'll happily volunteer to do the release manager bit if > desired. > 3) That very buggy features could be removed if the effort to fix > their bugs is sufficiently larger than the effort to migrate to the > ASM feature. > > Hen > > --------------------------------------------------------------------- > 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] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
