We have all agreed that some of the Jelly API needs to change. The thinking is along your line: it's been so long, we need the momentum on 1.0. Also, even API changes might not change the Tag API (or might leave room for backward compatibility), which is what allot of Jelly infrastructure is written to.
In terms of Marmalade, you just reminded me to go take a look... developer... pool... beginning... to.... dwindle. Kidding. The thing is that it's not, to my knowledge, seen nearly as much use a Jelly so you really can't compare the number of bug reports. Aside from something that cares about long compile times for the scripts or required pluggable expressions, what is Jelly unusable for? -----Original Message----- From: Simon Kitching [mailto:[EMAIL PROTECTED] Sent: Monday, June 13, 2005 9:41 PM To: Jakarta Commons Developers List Subject: Re: [jelly] distribution format On Tue, 2005-06-14 at 13:12 +1200, Simon Kitching wrote: > And > the lack of bugzilla entries and user/development questions also implies > that Jelly is fine as-is. umm .. the lack of Bugzilla entries is probably because Jelly uses Jira :-(. Jira has quite a few bug entries (73). It looks like there are quite a few bugs that really should be addressed before a 1.0 release because it looks to me like they have the potential to change Jelly behaviour - after a 1.0 release, that would mean going to 2.0 I believe. On the other hand, we need to consider that Jelly have any regular maintainers. And if Maven2 moves to Marmalade (marmalade.codehaus.org) instead of Jelly the developer pool will drop even further. So saying no to a 1.0 release now may mean saying no to a 1.0 release forever - despite the fact that Jelly is clearly useable for many purposes right now. I don't know which is the best choice... Regards, Simon --------------------------------------------------------------------- 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]
