james-server-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Burrell Donkin" <robertburrelldon...@gmail.com>
Subject Re: [PLANNING] Road map - lets find some consensus on .... release contents ....
Date Sat, 26 Jan 2008 07:16:46 GMT
On Jan 24, 2008 10:51 AM, Stefano Bagnara <apache@bago.org> wrote:
> Robert Burrell Donkin ha scritto:
> > On Jan 22, 2008 9:09 PM, Stefano Bagnara <apache@bago.org> wrote:
> >> IMHO stability of the API between components is a lesser priority
> >> compared to the config.xml+storage compatibility for an early release.
> >> The former is something targeting developers, the latter is something
> >> targeting every user.
> >
> > users are effected when an upgrade breaks a custom component
> >
> > ATM JAMES allows developers to create third party plugins but does not
> > clearly indicate which APIs are subject to change
>
> I just wanted to say that *all* of our upgrading users have a config.xml
> and stored mails to take care upgrading, while a minority have custom
> components (I would bet less than 10%, but this is just my personal guess).
>
> That's why I think config.xml and storage compatibility should be a
> greater priority compared to API stability.

JAMES needs more active developers. releasing unstable APIs damages
the development ecology.

- robert

---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org


Mime
View raw message