I think it is fine for the core but optional applications don't
necessarily have to stick to this schedule.
we have a lot of time for coding during the summer (no students, no
teachers ... lots of time for real work ;-) )
i also fear that a stabilization period from April to June, where all
applications have to be refactored to work on the new core and re-tested
+ the core applications itself have to be tested and bugfixed, might be
a littlebit short in case of big changes (like the ones proposed over
the last weeks).
Op 04/08/2011 09:48 AM, Philippe Van Eerdenbrugghe schreef:
May I have your opinion about the planning proposed in the wiki :
http://support.chamilo.org/projects/chamilo-20/wiki/Planning and would
that be possible to know how is going the future forum ?
Systho
Main steps¶
<http://support.chamilo.org/projects/chamilo-20/wiki/Planning#Main-steps>
- Planning & discussion about next main big works
- Feature Definition : What has to be done for the main big features
to be considered "done"
- Feature Implementation : Coding / Testing / Refactoring. Small
features which do not break anything can be added without needing
approval. Extra breaking features can be discussed to be added as well
but needs approval of the community.
- Feature Freeze : packages that will be part of the simultaneous
release must freeze their API / behaviour. The official list of those
package is communicated and everyone can checkout those package as a
dependency and know that it won't change until next simultaneous release.
- Stabilization : The API / behaviour cannot change but it is time to
hunt the bugs. The Translation team and the Documentation can do their
work.
- Simultaneous release : different "distributions" are made by
cherrypicking subsets of packages from the list of stable packages.
On a yearly basis¶
<http://support.chamilo.org/projects/chamilo-20/wiki/Planning#On-a-yearly-basis>
Since most of our clients are education institute, this proposal is
based to synchronize our schedule with the academic year beginning in
September, finishing in June, having July and Augustus as a period
with almost no user but very few devs also.
June : Simultaneous Release
July-Augustus-September : Planning
October - November - December : First Half for Implementation.
Planning might be redone.
January-February-March : Seconf Half for Implementation. Big features
should be done.
April : Feature freeze
April-May-June : Documentation & Translation
April-May-June : Bug Hunt / Manual Testing
_______________________________________________
Dev mailing list
Dev@lists.chamilo.org
http://lists.chamilo.org/listinfo/dev
_______________________________________________
Dev mailing list
Dev@lists.chamilo.org
http://lists.chamilo.org/listinfo/dev
