Reminder: GeoTools PMC members please vote on the financial support authorization.
Now that the code sprint is done, where did we get to: - The August 29th meeting notes had a good summary of progress and priorities - Ian got the styling api duplication resolved which is great (our minimum is met) - We decided not to make a milestone at the end of the code sprint, as we were both out of time and some work had not yet landed To help I volunteered to make the release-candidate "next weekend" as I had an upcoming long weekend available. What I did not notice until I returned from the code-sprint is ... that long weekend means this Monday! I am going to recommend we hold off setting up new branches until the final release is made; this would result in in a "code freeze" for bug/fixes and feedback which I believe is warrented. With that in mind: - CODE FREEZE (at least until release-candidate, although I recommend longer) - Check progress with pull-requests with GEOT-7287: https://github.com/geotools/geotools/pulls?q=is%3Apr+GEOT-7287 - Tasks/planning in google docs here <https://docs.google.com/document/d/12Jcmg49zjMaBz97FXwQ8qKSwUwih3kCWH8wy7dWsA3E/edit?usp=sharing> We REALLY wish to see this release-candidate play tested given the sheer amount of changes; our community has not responded well to calls for participation/testing and I wish to see this improve. -- Jody Garnett
_______________________________________________ GeoTools-Devel mailing list GeoTools-Devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geotools-devel
