On 12-03-27 09:22 AM, Christopher Brooks wrote:
>> 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
> 
> +1, though sometimes it's tough so this should be a goal and not a
> requirement
> 

Also, when people send out these emails they should make it clear which
components it affects.  If I'm only working on capture components then
it's not terribly important if someone's changing engage!  Adding things
like "engage, workflow" to the subject line to indicate that people
working with the engage and workflow systesm should pay attention will
reduce the chances of someone glossing over a message that they need to
read.

>> 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
> 
> +100
> 
> It's something we are doing with our features and I think it works
> well.  Even if it takes time to get a review done, starting them is
> important.

Especially now that we have a QA manager to browbeat developers who are
recalcitrant in creating, or performing, their reviews.  It's not, in my
opinion, my job nor the RM's job to create reviews for developers.  But
if that's what it takes to start getting code reviews done then I'll do
it.  We're suffering from a lack of polish that's really starting to get
annoying when man-days are lost while people try and figure out which
commit broke functionality.

G

> Chris


Attachment: signature.asc
Description: OpenPGP digital signature

_______________________________________________
Matterhorn mailing list
[email protected]
http://lists.opencastproject.org/mailman/listinfo/matterhorn


To unsubscribe please email
[email protected]
_______________________________________________

Reply via email to