opencog-dev team mailing list archive

[Cassio Pennachin <cassio@xxxxxxxxxxxxx>]

Hi,

> I like all of Cassio's recommendations. For everything but project  
> work that
> requires major change, how about a Linux-style regular cycle for  
> submitting
> private branches to Gama for merge into main? Say, every first  
> Monday of the
> month or something similarly easy-to-remember? Combined with a rule  
> that no
> private branch should go >2 months out of date, this would encourage  
> regular
> checkins (of course, each developer would be free to merge local  
> changes to
> a regularly-main-merged private branch at whatever frequency is  
> desired).
We'll have to tune this as we go, but this looks like a good enough  
starting point.  If anything, I'd encourage more frequent merging  
(say, never go >1 month out of date), but the exact parameters should  
be determined by the people actually doing the coding.  Alas, that  
doesn't include me at the moment...
Cassio