Simone: The voting is in the geotools mailing list and is financial only, I was only trying to remind folks to vote no that email thread.
This email is about logistics as I am trying to communicate what needs to be done across several projects to make a release candidate. -- Jody Garnett On Sep 4, 2023 at 6:33:13 AM, Simone Giannecchini < simone.giannecch...@geosolutionsgroup.com> wrote: > Hi Jody, > It is not super clear to me what we are voting for as there is a mix of > financial and technical update in this email. > > Just to be clear, we are voting solely on the split of the budget you > proposed in the document? > > Looking forward to hearing from you. > > Regards, > Simone Giannecchini > == > Online training classes for GeoNode, GeoServer and MapStore from the > experts! > Visit https://www.geosolutionsgroup.com/professional-training/ for more > information. > == > Ing. Simone Giannecchini > @simogeo > Founder/Director GeoSolutions Italy > President GeoSolutions USA > > phone: +39 0584 962313 > fax: +39 0584 1660272 > mob: +39 333 8128928 > US: +1 (845) 547-7905 > > http://www.geosolutionsgroup.com > http://twitter.com/geosolutions_it > > ------------------------------------------------------- > This email is intended only for the person or entity to which it is > addressed and may contain information that is privileged, confidential or > otherwise protected from disclosure. We remind that - as provided by > European Regulation 2016/679 “GDPR” - copying, dissemination or use of this > e-mail or the information herein by anyone other than the intended > recipient is prohibited. If you have received this email by mistake, please > notify us immediately by telephone or e-mail. > > > On Sun, Sep 3, 2023 at 4:37 PM Jody Garnett <jody.garn...@gmail.com> > wrote: > >> 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 >> _______________________________________________ >> Geoserver-devel mailing list >> Geoserver-devel@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/geoserver-develSimon >> >
_______________________________________________ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
