On Tue, Apr 21, 2009 at 4:24 PM, Markus Wiederkehr <[email protected]> wrote: > On Tue, Apr 21, 2009 at 3:23 PM, Robert Burrell Donkin > <[email protected]> wrote: >> On Tue, Apr 21, 2009 at 11:24 AM, Demetrios Kyriakis >> <[email protected]> wrote:
<snip> >>> For your users, this is the same chicken-egg problem like with the >>> documentation(found in quite a few Apache projects - not this one however) - >>> new users ask for documentation to be able to start at all, and they're >>> replied to contribute - but they can't cause they're not at that level yet - >>> they would need *the* documentation to get there where they could contribute >>> at all. >> >> if you want to use 3.x then IMO you really need to be an active >> contributor to the community. AIUI most 3.x deployments are forks, and >> the codebase is neither mature nor production proved. so yes, it's a >> chicken-and-egg situation with 3.x - it won't be ready for release >> until it's been proved in production but it's unlikely to be proved >> until it's more widely used. > > Then you have to cut an alpha release (and if no one evaluates the > alpha you're doomed). at apache, alpha usually implies a push towards a final release. a milestone would be appropriate. > IMHO a release should at least be a goal of the project. "Release > early, release often." i agree but conflicts over releases were the major historic issue afflicting the james development community going has been very slow with the dependent libraries. the wider development community can find only a limited amount of time. i have a range of other interests and i'm not interested in driving james development forward alone. i'm happy to wait until either existing developers have more time or new contributors become active. - robert --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
