On Jan 23, 2008 12:13 AM, Steve Brewin <[EMAIL PROTECTED]> wrote: > [EMAIL PROTECTED] on 22 January 2008 23:47 wrote: > > To: James Developers List > > Subject: Re: [PLANNING] Road map - lets find some consensus on .... > > release contents .... > > > > > > > ATM JAMES allows developers to create third party plugins > > but does not > > > clearly indicate which APIs are subject to change > > > > +1 API's need to be an early target. > > > > d. > Would it be possible to further classify Stefano's excellent list of new > functionality in trunk to indicate which rely on none, minor or major API and > schema changes?
sounds like a plan > Then we could evaluate what is the 'low hanging fruit' that we could most > easily harvest for an initial milestone drop. for a 3.0 milestone, trunk would be fine anyway but understanding the APIs required for each feature would allow better planning for a 2.5 from the trunk code base. it would also make it much easier to take another look at revising the module system to make this easier. - robert --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
