The recent post 1.3 merge has seen quite a bit of new code that has made its way to trunk. Looking through the additions made me realize that we should probably get back to the practice of
a) Announcing features and changes that are either to be implemented or to be merged on list. This would give the other developers a heads up that certain areas of the code may see changes here and there. In addition, those interested get the ability to keep on eye on the latest developments. b) More complex features need documentation anyway, which leads to the idea (brought up by Josh quite some time ago) that these features should be described with their objectives and implementation proposal on a wiki page. This page would then be transformed into feature documentation. c) After code has been checked in, a code review should be opened and made available to interested developers, maybe as part of an announcement on list. This would serve a couple of purposes: 1. code quality is likely to be increased. 2. developers would be informed that a certain feature has been fully implemented. For all of this, it would probably make sense to try and get back to story writing and the creation of subtasks. Features would be discussed in the context of user stories, and the completion of user story would lead to a quick announcement on list coupled with a code review. Tobias _______________________________________________ Matterhorn mailing list [email protected] http://lists.opencastproject.org/mailman/listinfo/matterhorn To unsubscribe please email [email protected] _______________________________________________
