cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Bertrand Delacretaz <>
Subject Re: [Proposal] Document development/maintenance practices
Date Tue, 09 Mar 2004 15:37:05 GMT
Le Mardi, 9 mars 2004, à 16:27 Europe/Zurich, Tim Larson a écrit :

> ...I propose we create a document detailing the practices
> and policies we follow to minimize this risk to users of Cocoon.

Sounds good.

> ...  Maintaining a change log to help with upgrades

And our CVS has all the details

>   Strongly avoiding breaking interfaces

And indicating what's more stable or more subject to change

>   Conducting open, public discussion of design and development
>   Querying userbase to determine impact of potential changes
>   Responding to the userbase, even reverting changes when necessary
>   Voting on major additions, changes, deprecations, and removals
>   Deprecating interfaces instead of immediately dropping support
>   Only allowing code that has a community to support it
> What do others think about developing a document like this
> to document our guidelines and improve our marketability?

I like the idea, maybe you can start something on the wiki?

> Do we already have a document like this somewhere?

I don't think so.


View raw message