The additional overhead for backports is a good point Andrea and one I had not thought of; one we could mitigate slightly with planning.
aside: I should note that the funds raised thus far are not exclusively for GeoTools; some availability or code sprint will be required for downstream projects to make the change.I expect many will not be in position to notice until after a stable release is made. So we should plan for API migration this release cycle Q3/Q4; and then to host a code sprint or office hours or something for downstream projects to migrate in Q4. - April 21-23: Apache / OGC / OGC Code sprint - good opportunity but too soon - July 1-2: FOSS4G - very small sprint maybe suitable for proof-of-concept and planning what to do on package by package basis - August 21 - September 1: Bolsean - this is a good candidate but *very* close to our RC deadline I expect supporting other projects will need to be an online sprint; suggest: "last friday of the month" drop in office hours. -- Jody Garnett On Tue, Mar 21, 2023 at 2:00 AM Andrea Aime < andrea.a...@geosolutionsgroup.com> wrote: > Hi Jody, > agreed, we cannot afford having two large APIs shifts in sequence, each > one will have ramification > both in terms of downstreams projects affected, and in terms of time, as > it will make backports harder > to deal with. > > As a big API break it will be limited to the main branch, while stable and > maintenance will remain on > the previous one, meaning all backports will need some amount of rewriting > (if we do it right, mostly imports). > We'll also need some time for the waters to settle before we can cut a > release, it's not something we > can do, say, in August, to release right afterwards in September. > > So I'd expect the change to cause friction in the project for 6-12 months > after it landed, increasing > all contribution costs. > > The plan proposed looks good, and also the bare minimum for acceptance. > +1 > > Cheers > Andrea > > On Mon, Mar 20, 2023 at 8:23 PM Jody Garnett <jody.garn...@gmail.com> > wrote: > >> This was discussed <https://git.osgeo.org/gitea/osgeo/todo/issues/142> >> earlier >> as part of OSGeo budget allocation >> <https://wiki.osgeo.org/wiki/OSGeo_Budget_2023#OSGeo_Initiatives>. >> >> Before proceeding with fundraising and setting up an osgeo initiative I >> want to confirm with the GeoTools PMC that this is a good idea and we are >> okay with doing the work if funding / planning / enthusiasm are in place to >> complete the activity. >> >> The proposal is here, and the approach has been discussed in prior >> meetings: >> - https://github.com/geotools/geotools/wiki/Remove-OpenGIS >> -- >> Jody Garnett >> _______________________________________________ >> GeoTools-Devel mailing list >> GeoTools-Devel@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/geotools-devel >> > > > -- > > Regards, > > Andrea Aime > > == > GeoServer Professional Services from the experts! > > Visit http://bit.ly/gs-services-us for more information. > == > > Ing. Andrea Aime > @geowolf > Technical Lead > > GeoSolutions Group > phone: +39 0584 962313 > > fax: +39 0584 1660272 > > mob: +39 339 8844549 > > https://www.geosolutionsgroup.com/ > > http://twitter.com/geosolutions_it > > ------------------------------------------------------- > > Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE > 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si > precisa che ogni circostanza inerente alla presente email (il suo > contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è > riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il > messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra > operazione è illecita. Le sarei comunque grato se potesse darmene notizia. > > 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 >
_______________________________________________ GeoTools-Devel mailing list GeoTools-Devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geotools-devel
