Changes between Initial Version and Version 1 of MapGuideRfc171

Timestamp:

05/21/19 08:48:18 (6 years ago)

Author:

jng

Comment:

--

MapGuideRfc171

@@ +1 @@
+
+= !MapGuide RFC 171 - Update version number to 4.0 =
+
+This page contains a change request (RFC) for the !MapGuide Open Source project.
+More !MapGuide RFCs can be found on the [wiki:MapGuideRfcs RFCs] page.
+
+== Status ==
+
+||RFC Template Version||(1.0)||
+||Submission Date||||
+||Last Modified||||
+||Author||Jackie Ng||
+||RFC Status||draft||
+||Implementation Status||Ready for review||
+||Proposed Milestone||4.0||
+||Assigned PSC guide(s)||(when determined)||
+||'''Voting History'''||(vote date)||
+||+1||||
+||+0||||
+||-0||||
+||-1||||
+||no vote|| ||
+
+== Overview ==
+
+This RFC proposes to set the version number of the next MapGuide release to be 4.0
+
+== Motivation ==
+
+The volume of changes and features implemented so far is such that 3.3 is better represented as 4.0
+
+The other motivation is that there is pending development work that will have "breaking change" ramifications for MapGuide Application Developers, so bumping the version to 4.0 will pre-emptively set such expectations.
+
+== Proposed Solution ==
+
+Set the base version number in MapGuide to 4.0.0.0
+
+Ensure that any doxygen content for APIs introduced in this development cycle are set to `\since 4.0`
+
+Update all version references in code to `3.3` to `4.0`
+
+Update all version references in XML schemas to `3.3.0` to `4.0.0`
+
+All adopted RFCs thus far in this cycle will be retroactively updated to target the `4.0` milestone
+
+== Implications ==
+
+
+
+== Test Plan ==
+
+Run existing test suite to ensure no breakages
+
+== Funding / Resources ==
+
+Community