-
Notifications
You must be signed in to change notification settings - Fork 9
PSC Meeting 2015 12 14
- Introduction to RFC #5 Updates.
- What changes for users
- What could possible change in future versions.
Conclusions: Leave old services in for the 2.9 version but add in new rfc5 work. To assist users:
-
Write disclaimers and place them in the code an release notes.
-
Write a 2.8->2.9 services migration guide based on the new mapbook.
-
Categorizing the next two wave of updates:
-
The Closeness of 2.8.2 and 2.9 and the need to replace 2.8.1 (MS4W version/code conflicts)
-
2.10 and the inclusion of RFC #5 updates.
-
I'm nominating (a head of the meeting) to name Jim release master for the 2.9 series as well. This is a bit of a formality but I want it formalized.
Conclusions:
-
Release a 2.8.2 with a ‘harmonizing’ fix for the current MS4W release.
-
Release 2.9 at the same time with the new features from RFC #5.
-
2.9 = RFC#5, HashTrack updates.
-
2.9.2/2.10.0 = Fix all of the legends issues on the mailing list.
-
Google + Tablets bug will be tabled for a Future release when we update the underlaying libraries.
-
theduckylittle moved jklassen be release manager. jklassen accepts. +1 from EliL, Brent, Blammo
-
MediaWiki
-
Duck will research archiving.
-
Jklassen will post to the user’s list saying it will be deprecated.
-
GeoMOOSE 3.0, General Conclusions:
-
Libraries need up-"ported" Dojo 1.Latest and OL3 require rewriting a large amount of code.
-
Level of Effort and Hours Required are both estimated very high by Duck.