Changes between Version 2 and Version 3 of MapGuideRfc25


Ignore:
Timestamp:
Aug 8, 2007, 6:25:51 PM (15 years ago)
Author:
jasonchen
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • MapGuideRfc25

    v2 v3  
    88 
    99||RFC Template Version||(1.0)||
    10 ||Submission Date||(Date/Time submitted)||
     10||Submission Date||August 8, 2007||
    1111||Last Modified||Jason Chen [[Timestamp]]||
    1212||Author||Jason Chen||
    13 ||RFC Status||(draft, proposed, frozen for vote, adopted, retracted, or rejected)||
    14 ||Implementation Status||under development)||
    15 ||Proposed Milestone||1.1||
     13||RFC Status||proposed (draft, proposed, frozen for vote, adopted, retracted, or rejected)||
     14||Implementation Status||under development||
     15||Proposed Milestone||1.3||
    1616||Assigned PSC guide(s)||(when determined)||
    17 ||'''Voting History'''||(vote date)||
    18 ||+1|| ||
     17||'''Voting History'''||August 8, 2007||
     18||+1||Tom, Chris, Bruce, Trevor, Jason||
    1919||+0|| ||
    2020||-0|| ||
     
    4343== Test Plan ==
    4444
    45 How the proposed change will be tested, if applicable.  New unit tests should be detailed here???
     45Tests need to be done after the upgrade:
     46
     47    * Resource Service unit tests must all pass.
     48    * Feature Service unit tests must all pass.
     49    * API test pages should be checked against the affected APIs.
    4650
    4751== Funding/Resources ==
    4852
    49 This section will confirm that the proposed feature has enough support to proceed.  This would typically mean that the entity making the changes would put forward the RFC, but a non-developer could act as an RFC author if they are sure they have the funding to cover the change.
     53Supplied by Autodesk.