[sakai2-tcc] Which parts of the code need a mandatory review of changes

[Neal Caidin]

Hi J-F,

I'm not sure if I understand your comment. Is it about having code reviews?  What kind of list do you want?

A couple of thoughts/questions wrt Code Review:

1) Maybe discussing the review process is a question for the CLE release team and not TCC?

2) The existing "process" seems to be to ask for help in reviewing, over email list or on the CLE release team calls.

3) Do we need a better defined process for reviews, and if so, how realistic is it that the process will be complied with?

4) I'm still looking into Crucible, but that is just a tool to make reviews easier, it does not solve the process issue.

2 cents.

Cheers,
Neal



On Jul 17, 2013, at 8:40 AM, Jean-Francois Leveque <jean-francois.leveque at upmc.fr> wrote:

> Hi,
> 
> This subject was part of the Thursday meeting in San Diego.
> 
> I remember kernel and access being mentioned and I understand portal is 
> also important.
> 
> I would really like to have a list instead of learning by trying because 
> this might not be obvious for all of us.
> 
> I would also like this review process to be defined. The questions I 
> could ask start with How, Who and How often.
> 
> Cheers,
> 
> J-F
> _______________________________________________
> sakai2-tcc mailing list
> sakai2-tcc at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/sakai2-tcc