[kepler-dev] Monday, April 25: code cleaning, followed by code freeze
cxh at eecs.berkeley.edu
Fri Apr 22 13:46:02 PDT 2005
> From: "Christopher Brooks" <cxh at eecs.berkeley.edu>
> To: ptresearch at maury.eecs.berkeley.edu
> Subject: [Ptolemy] Monday, April 25: code cleaning, followed by code freeze
> Date: Fri, 22 Apr 2005 13:38:33 -0700
> On Monday, April 25, I will be cleaning the code.
> I plan on reindenting and shortening up the lines so that when
> we print the code for review, it looks better. Edward suggested
> we try longer lines, but I think we are better off with shorter lines.
> I'll do the usual cleanups as well.
> Any changes that you check in on Monday might get accidentally
> overwritten. I suggest checking out a new tree when I give the
> all clear on Monday evening.
> My plan is to have cds ready for testing on Tuesday, May 3.
> Thus, I would like to have a code freeze on from Monday, April 25 to
> Tuesday, May 3. What does a code freeze mean? It means that you
> should not check in anything that will break the build. In
> particular, be very careful about adding new directories to code that
> is shipping. The code freeze to not particularly apply to code
> we are not shipping (backtrack, codegen).
> Ptolemy maillist - Ptolemy at chess.eecs.berkeley.edu
More information about the Kepler-dev