[Mitgcm-support] Re: CVS Policy

[mitgcm-support at dev.mitgcm.org]

 I would like to keep distributions/ - that will be used for
core model "releases". We don't have one because 
the sensitivity stuff isn't quite ready yet. But we will
have one soon. Same goes for an ECCO environment "release"
I imagine.

 packages/ could be useful if we get to the point of
Samar, Sandrine, Mick, Brian, Ralf, etc.... providing
their packaged code directly to people. 

 I had been leaving core policy (cvs, packaging,.. ) documents 
in low-format, non-html style i.e. e-mail, palm-pilot,
newsgroup etc... friendly ( a sort of RFC, IEN, ... approach )

 Main thing is to write down what discipline/work practices we 
are imposing on ourselves for the core model development line. 
Goals should still be

 o concurrent development should be the norm.

 o integration should be easy, rapid, organised, clear and
   useful!

 o the MAIN branch should not get full of broken or
   half-finished work.

Chris
 
Alistair Adcroft wrote:
> 
> Patrick Heimbach wrote:
> > It's under  http://mitgcm.org/cgi-bin/cvsweb/cvspolicy.html
> 
> You mean "It's right under my nose"!!
> 
> I just converted cvspolicy.html into HTML since it wasn't.
> 
> Looking through the CVS repository, shall we delete "packages"
> and "distributions" since we haven't followed that idea?
> 
> A.