From tcraig at ucar.edu Tue Feb 10 09:20:33 2004 From: tcraig at ucar.edu (Tony Craig) Date: Tue Feb 10 09:21:45 2004 Subject: [CCSM-CRB] CCSM3 Release Date, June 2, 2004 Message-ID: FYI and in case you haven't heard, the release date for CCSM3 has been pushed back to June 2. Schedules and milestones for the release will be updated to reflect this new date. I do not expect the release date to be changed again unless there are extreme circumstances largely outside our control. This change gives us an extra 2 weeks to put effort into the release to improve quality and still allows us to have the release out a month before the summer meeting. Also, this still meets the "release by" date set by the SSC. Brian Kauffman will be coordinating preparation of the release. There is a CCSM3 release plan linked off the CSEG page, www.cgd.ucar.edu/cseg. CSEG will be spending most of their time over the next few months helping finalize model configurations, testing, documenting, doing control runs, preparing model input and output datasets, and getting the web site ready. If you have any questions, please feel free to contact Brian or myself. tony.......... From kauff at cgd.ucar.edu Thu Feb 26 13:23:14 2004 From: kauff at cgd.ucar.edu (Brian Kauffman) Date: Thu Feb 26 15:36:00 2004 Subject: [CCSM-CRB] ccsm3.0 release - code freeze dates In-Reply-To: Message-ID: CCSM-CRB, CSEG has put together a CCSM3.0 release timetable which is available at http://www.cgd.ucar.edu/cseg/csm3.0/checklist/checklist_milestones.html It remains very similar to the time table presented at the 2003 Dec 15 CCRB meeting, the notes of which are available at http://www.ccsm.ucar.edu/management/CCRB There are a few dates of particular importance... Mar 15 create a CCSM tag with unified vector/scalar code Apr 1 FREEZE CCSM3: BFB (on IBM wrt 1990 controls ~ IPCC mode OFF) that means all subsequent code changes must be bit-for-bit Apr 30 FREEZE CCSM3: SRC CODE AND DATA SETS that's the cut off date for all changes to source code, this allows one month of final testing, bug fixes, and preparation for release Jun 2 release available to the public If anyone feels this schedule is not OK, please raise the issue ASAP with Bill Collins and/or the CCRB. thanks, -Brian