Changes between Version 2 and Version 3 of MapGuideRfc25

Timestamp:

08/08/07 18:25:51 (17 years ago)

Author:

jasonchen

Comment:

--

MapGuideRfc25

@@ -8 +8 @@
  
 ||RFC Template Version||(1.0)|| 
-||Submission Date||(Date/Time submitted)||
+||Submission Date||August 8, 2007||
 ||Last Modified||Jason Chen [[Timestamp]]||
 ||Author||Jason Chen||
-||RFC Status||(draft, proposed, frozen for vote, adopted, retracted, or rejected)||
-||Implementation Status||under development)||
-||Proposed Milestone||1.1||
+||RFC Status||proposed (draft, proposed, frozen for vote, adopted, retracted, or rejected)||
+||Implementation Status||under development||
+||Proposed Milestone||1.3||
 ||Assigned PSC guide(s)||(when determined)||
-||'''Voting History'''||(vote date)||
-||+1|| ||
+||'''Voting History'''||August 8, 2007||
+||+1||Tom, Chris, Bruce, Trevor, Jason||
 ||+0|| ||
 ||-0|| ||
@@ -43 +43 @@
 == Test Plan ==
 
-How the proposed change will be tested, if applicable.  New unit tests should be detailed here???
+Tests need to be done after the upgrade:
+
+    * Resource Service unit tests must all pass.
+    * Feature Service unit tests must all pass.
+    * API test pages should be checked against the affected APIs.
 
 == Funding/Resources ==
 
-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.
+Supplied by Autodesk.