Deprecation announces an intention to remove. One of the main reasons given
in the jira tickets I saw for deprecation sooner rather than later, is to
ensure discussions happen and replacements, migrations and I assume even
possibly decisions not to deprecate after all can be well sorted out and
the community well prepared before action is required. So the goal as I've
understood it (I'm only a committer not a PMC member, so this is just my
opinion/observation) is precisely to create some "splash" get people's
attention and make sure this is discussed thoroughly. Definitely feel free
to contribute your thoughts and concerns in a constructive manner. This is
a community and your voice matters, and it's open source so you also have
the power to contribute.
On Fri, Jul 17, 2020 at 2:56 AM Bernd Fehling <
bernd.fehl...@uni-bielefeld.de> wrote:
> At first glance I see many Deprecations but also many TBD at Package
> location. :-(
>
> To understand this right, you kicked out the code and now waiting
> for the community to take over and reinvent the wheel?
>
> Or are there any recent plans of the PMC members to at least start
> Package locations on github and then let the community take over?
>
> Or what?
>
> I'm following this list for many years but where were the discussions
> about these decisions?
>
> Regards
> Bernd
>
>
> Am 17.07.20 um 07:47 schrieb Ishan Chattopadhyaya:
> > Hi Solr Users,
> > Here is a list of recent and upcoming deprecations in Solr 8.x.
> > https://cwiki.apache.org/confluence/display/SOLR/Deprecations
> >
> > Please feel free to chime in if you have any questions. You can comment
> > here or in the specific JIRA issues.
> >
> > Thanks and regards,
> > Ishan Chattopadhyaya
> >
>
--
http://www.needhamsoftware.com (work)
http://www.the111shift.com (play)
