J3/05-005 page 1 of 1 Date: 2005 July 30 To: J3 From: Dan Nagle Subject: WG5 Schedule for Fortran 2008 J3's Response to WG5-N1590, adopted at during the Joint Meeting with J3 during 2004 July in Las Vegas J3 concurs with WG5's intentions as expressed in N1590 with respect to the revised schedule for Fortran 200x. Stages of the Development of Fortran 200x, and the J3 anticipated schedule J3 Meeting & Date Major Agenda Focus ----------------- ------------------ J3 168 2004 May Nominate Features J3 169 2004 August Nominate Features J3 170 2004 November Nominate Features J3 171 2005 February Nominate Features WG5/J3 Joint 172 2005 May Choose Features J3 173 2005 August Define Features J3 174 2005 November Define Features WG5/J3 Joint 175 2006 February Final Features J3 176 2006 May Complete Features J3 177 2006 August Review Draft (A/B/C) J3 178 2006 November Review Draft (A/B/C) J3 179 2007 February Review Draft (A/B/C) J3 180 2007 May Review Draft (Plenary) J3 181 2007 August Final Draft J3 182 2007 November Process Comments J3 183 2008 February Final Review J3 184 2008 May Pass to WG5 J3 185 2008 August J3 186 2008 November J3 186 2009 February J3 187 2009 May J3 188 2009 August The Wg5 process and stages is below Stage Process ----- ------- 1 Repository started 2004-05 Preliminary choice of significant features 2005-04 Final choice of significant features 2006-02 Completion of separate edits 2006-05 2 New Work Item proposed to SC22 2006-08 First working draft available 2007-05 WG5 review of working draft 2007-07 WG5 approval of draft CD 2007-09 3 First CD submitted for registration and approval 2007-10 First CD ballot initiated 2007-10 First CD ballot comments available 2008-01 WG5 ballot resolution meeting 2008-02 WG5 review meeting 2008-07 Final CD submitted for approval 2008-09 Final CD ballot initiated 2008-10 Final CD ballot comments available 2009-02 WG5 approval of draft DIS 2009-04 4 DIS registered 2009-05 DIS ballot initiated 2009-05 DIS ballot results available 2009-07 5 Standard published 2009-08 Notes. A. This plan is based on the assumption that we aim for a minor revision in 5 years time, much as for Fortran 90/95. Reasons: 1. Vendors will need time to implement all of Fortran 2003, 2. Vendors will need time to optimize any of Fortran 2003, 3. Users will need time to learn much of Fortran 2003, 4. Users will need time to learn where Fortran 2003 needs improvement, 5. Authors will need time to prepare textbooks and other media supporting Fortran 2003, 6. Vendors will need time to keep the on-going costs of developing Fortran compilers within that which may be recouped from the on-going sales of Fortran processors, and 7. A minor update is indicated by the alternation between major and minor updates experienced so far.