Hi Jan, Just trying to make sure I understand your suggestion. Are you suggesting:
(1) that we announce v1 as deprecated at "V2-API-Complete" (instead of the later "v2-API-used-internally")? Or... (2) that we plan "v2-API-used-internally" to coincide with 10.0? (3) Or both? Best, Jason On Mon, Oct 31, 2022 at 5:04 PM Jan Høydahl <[email protected]> wrote: > > Thanks for a thorough SIP. > > Wrt deprecation plan, could we not have "v2-API-Complete" in e.g. 9.5 (and > deprecate v1). Then we wait until 10.0 with "v2-API-used-internally", and > 11.0 for removing v1. Say we release 10.0 in March 2023, then the new main > will be 11.0 and we can already remove v1 in main. > > Looking forward to code generating SolrJ classes. And perhaps community > members actively using some other prog.language will be empowered to auto > generate 90% of such clients. > > Jan > > > 31. okt. 2022 kl. 21:23 skrev Jason Gerlowski <[email protected]>: > > > > Hey all, > > > > This morning I published SIP-16, which proposes the changes necessary > > to "finish" (i.e. plug coverage gaps and polish) Solr's v2 APIs and a > > path to deprecating Solr's v1 APIs. > > > > The SIP can be found here: > > https://cwiki.apache.org/confluence/display/SOLR/SIP-16%3A+Polish+and+Prepare+v2+APIs+for+v1+Deprecation > > > > Please read the SIP description and come back here for discussion. As > > the discussion progresses we will update the SIP page with any > > outcomes and eventually move things to a VOTE (or lazy consensus). > > > > Looking forward to hearing your feedback! > > > > Best, > > > > Jason > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [email protected] > > For additional commands, e-mail: [email protected] > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
