See JIRA, there's a bug in the PR which means the change did not go through. I pinged infra on slack. If this is not unblocked by tonight, I'm happy to commit your public key for you, I see your key ID 7AA80271 in https://people.apache.org/keys/committer/
Jan > 26. apr. 2023 kl. 14:53 skrev Justin Sweeney <justin.sweene...@gmail.com>: > > Looks like https://issues.apache.org/jira/projects/INFRA/issues/INFRA-24485 > is still unresolved to get write access to committers, or at least I am > still unable to write my key there. > > If this continues to be an issue today, would a PMC member be willing to > commit the updated KEYS file assuming I send them my key to add? Just > hoping that we can unblock the release by moving past this step and open up > the release to be smoke tested. > > Justin > > On Sun, Apr 23, 2023 at 10:27 PM David Smiley <dsmi...@apache.org> wrote: > >> I see no reason for a vote as there is no change to vote on relative to how >> this project has done things prior to the project split, and we didn't vote >> for it to be different for the project split. >> >> Anyway, it looks like the change is done now. >> >> Separate point: I don't think this is a big deal that a PMC member might be >> needed for particular steps. Many of us should be happy to help (certainly >> myself included). >> >> ~ David Smiley >> Apache Lucene/Solr Search Developer >> http://www.linkedin.com/in/davidwsmiley >> >> >> On Fri, Apr 21, 2023 at 6:15 PM Ishan Chattopadhyaya < >> ichattopadhy...@gmail.com> wrote: >> >>> In this particular matter, there's absolutely no need. Anyway, I think it >>> is water under the bridge now, unless someone from PMC comes back a few >>> days later and, bizzarely, votes against letting committers push to the >> SVN >>> server (something we've always allowed in the past, before 9.0). >>> >>> On Sat, 22 Apr, 2023, 12:28 am Mike Drob, <md...@mdrob.com> wrote: >>> >>>> Eid Mubarak to all who celebrate and happy Friday to everybody else. >> And >>>> happy weekend to those who want to rest and not check emails >> constantly. >>>> And hey, wouldn't you know it, the next workday isn't until 72 hours >>> away! >>>> Let's try to be accommodating to all of our friends, yes? >>>> >>>> On Thu, Apr 20, 2023 at 6:15 PM Ishan Chattopadhyaya < >>>> ichattopadhy...@gmail.com> wrote: >>>> >>>>> 24 hours are enough to cover all timezones on earth. Only those on >>> other >>>>> planets need more time. >>>>> >>>>> On Fri, 21 Apr, 2023, 4:42 am Jan Høydahl, <jan....@cominvent.com> >>>> wrote: >>>>> >>>>>> Bureaucracy sure, but needless? Don't think so. How else can we >> make >>>>>> decisions across time zones and national holidays that ensures >> every >>>> PMC >>>>>> member has a chance to vote? Of course, in this matter it would >>>> probably >>>>> be >>>>>> possible to persuade INFRA to let Solr "inherit" Lucene's policy >>>>>> immediately, and then change it back, only if a PMC vote demands >>> it... >>>> :) >>>>>> >>>>>> Jan >>>>>> >>>>>>> 21. apr. 2023 kl. 01:01 skrev Ishan Chattopadhyaya < >>>>>> ichattopadhy...@gmail.com>: >>>>>>> >>>>>>> Vote and 3 days of wait!? This whole Apache process feels like a >>>>> needless >>>>>>> bureaucracy, stuck in the twentieth century. If such a vote is a >>>> strict >>>>>>> necessity, I think we should also get a vote on whether to stick >>> with >>>>>>> Apache. >>>>>>> >>>>>>> On Fri, 21 Apr, 2023, 3:52 am Justin Sweeney, < >>>>>> justin.sweene...@gmail.com> >>>>>>> wrote: >>>>>>> >>>>>>>> I believe I can continue the release for most of the steps >> before >>>> this >>>>>> will >>>>>>>> be a blocking issue. If as a result of the vote, it is decided >> not >>>> to >>>>>> grant >>>>>>>> write permissions to non-PMC committers, I'd just need >> additional >>>>>> support >>>>>>>> from a PMC member to complete the 9.2.1 release. >>>>>>>> >>>>>>>> On Thu, Apr 20, 2023 at 6:08 PM Jan Høydahl < >>> jan....@cominvent.com> >>>>>> wrote: >>>>>>>> >>>>>>>>> Ah, I never knew this was the default. I see no reason to >> change >>>> our >>>>>>>>> release practice, so guess we can do a proper VOTE and wait 3 >>> days >>>>> for >>>>>> it >>>>>>>>> to complete before the release can happen. I suppose several RM >>>> steps >>>>>> can >>>>>>>>> happen before this is a blocker, or? >>>>>>>>> >>>>>>>>> Jan >>>>>>>>> >>>>>>>>>> 20. apr. 2023 kl. 22:24 skrev Houston Putman < >>> hous...@apache.org >>>>> : >>>>>>>>>> >>>>>>>>>> Ahhh I think I know the issue. We haven't had a non-pmc >>> committer >>>>> do a >>>>>>>>>> release since the Lucene/Solr split. I guess Lucene was setup >> to >>>>>>>> support >>>>>>>>>> this, but by default Apache doesn't allow it, so Solr doesn't >>> have >>>>> it >>>>>>>>>> enabled now. >>>>>>>>>> >>>>>>>>>> As per the JIRA infra can do this. Should we get a PMC vote on >>>> this? >>>>>>>>>> >>>>>>>>>> - Houston >>>>>>>>>> >>>>>>>>>> On Thu, Apr 20, 2023 at 4:06 PM Houston Putman < >>>> hous...@apache.org> >>>>>>>>> wrote: >>>>>>>>>> >>>>>>>>>>> I commented. >>>>>>>>>>> >>>>>>>>>>> On Thu, Apr 20, 2023 at 3:59 PM Justin Sweeney < >>>>>>>>> justin.sweene...@gmail.com> >>>>>>>>>>> wrote: >>>>>>>>>>> >>>>>>>>>>>> I've created an Infra ticket here: >>>>>>>>>>>> https://issues.apache.org/jira/browse/INFRA-24485. It would >>>>>> probably >>>>>>>>> be >>>>>>>>>>>> useful if a few PMC members can comment support for it, I am >>> not >>>>>> sure >>>>>>>>>>>> what an approval process looks like for this. >>>>>>>>>>>> >>>>>>>>>>>> On Thu, Apr 20, 2023 at 3:44 PM Jan Høydahl < >>>>> jan....@cominvent.com> >>>>>>>>>>>> wrote: >>>>>>>>>>>> >>>>>>>>>>>>> +1 to give svn release permission to all committers! >>>>>>>>>>>>> >>>>>>>>>>>>> Jan Høydahl >>>>>>>>>>>>> >>>>>>>>>>>>>> 20. apr. 2023 kl. 18:01 skrev Houston Putman < >>>>> hous...@apache.org >>>>>>> : >>>>>>>>>>>>>> >>>>>>>>>>>>>> Yeah it definitely seems like a change in policy. >>>>>>>>>>>>>> >>>>>>>>>>>>>> Justin already can't add his GPG key to the KEYS file, so >> we >>>>> know >>>>>>>>>>>> this is >>>>>>>>>>>>>> going to be a blocker now and again when the release vote >>>>> passes. >>>>>>>>>>>>>> >>>>>>>>>>>>>> The infra page does say "*By default*, only PMC/PPMC >> members >>>>> have >>>>>>>>>>>> write >>>>>>>>>>>>>> access to the dist/release directories." So it seems like >> we >>>> can >>>>>>>>>>>> change >>>>>>>>>>>>>> that for solr if we want to. I have no problem reverting >> to >>>> the >>>>>> old >>>>>>>>>>>>>> permission scheme, since committers will not be able to do >>>>>> releases >>>>>>>>>>>>>> otherwise. >>>>>>>>>>>>>> >>>>>>>>>>>>>> - Houston >>>>>>>>>>>>>> >>>>>>>>>>>>>>> On Thu, Apr 20, 2023 at 11:38 AM Jan Høydahl < >>>>>>>> jan....@cominvent.com >>>>>>>>>> >>>>>>>>>>>>> wrote: >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> It has not been a blocker before, so I’d just proceed >> with >>>> the >>>>>>>>>>>> release >>>>>>>>>>>>> and >>>>>>>>>>>>>>> ask again if it becomes a problem. Non-pmc committers >> have >>>>>>>> certainly >>>>>>>>>>>>> been >>>>>>>>>>>>>>> RM before. >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Jan Høydahl >>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> 20. apr. 2023 kl. 17:19 skrev Justin Sweeney < >>>>>>>>>>>>> justin.sweene...@gmail.com >>>>>>>>>>>>>>>> : >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> While working on the 9.2.1 release process, I've hit a >>> bit >>>>> of a >>>>>>>>>>>>>>> blocker. It >>>>>>>>>>>>>>>> looks like you must be a PMC member to push to >>>>>>>>>>>>>>>> https://dist.apache.org/repos/dist/release/solr (based >> on >>>>>>>>>>>>>>>> https://infra.apache.org/release-publishing.html#normal >>> and >>>>>>>>>>>>>>>> >>>>> https://the-asf.slack.com/archives/CBX4TSBQ8/p1682001736232839 >>>>>> ). >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> This might primarily be a question for @David Smiley < >>>>>>>>>>>>> dsmi...@apache.org> >>>>>>>>>>>>>>> but >>>>>>>>>>>>>>>> noticed his slack status is on vacation so wanted to >> raise >>>> it >>>>>>>> here >>>>>>>>>>>> for >>>>>>>>>>>>>>> the >>>>>>>>>>>>>>>> group. >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Should we modify the permissions to allow any Solr >>> committer >>>>> to >>>>>>>>>>>> push to >>>>>>>>>>>>>>>> that SVN repo or should we restrict releases to PMC >>> members? >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> I am assuming I can open an Infra ticket to change >>>>> permissions, >>>>>>>> but >>>>>>>>>>>> it >>>>>>>>>>>>>>> will >>>>>>>>>>>>>>>> likely require some approvals beyond myself. >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Justin >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> On Thu, Apr 20, 2023 at 10:21 AM Justin Sweeney < >>>>>>>>>>>>>>> justin.sweene...@gmail.com> >>>>>>>>>>>>>>>>> wrote: >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> Yup, feel free to go ahead and merge that in. >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> On Thu, Apr 20, 2023 at 10:18 AM Ishan Chattopadhyaya < >>>>>>>>>>>>>>>>> ichattopadhy...@gmail.com> wrote: >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> Hi Justin, >>>>>>>>>>>>>>>>>> Do we have time to merge the following, please? >>>>>>>>>>>>>>>>>> https://issues.apache.org/jira/browse/SOLR-16741 >>>>>>>>>>>>>>>>>> Thanks and regards, >>>>>>>>>>>>>>>>>> Ishan >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> On Thu, 20 Apr 2023 at 19:37, Justin Sweeney < >>>>>>>>>>>>>>> justin.sweene...@gmail.com> >>>>>>>>>>>>>>>>>> wrote: >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> Thanks for merging that, I'm just getting started >> along >>>> the >>>>>>>>>>>> release >>>>>>>>>>>>>>>>>>> process, had to get a gpg key setup but should be >>> moving >>>>>>>> today. >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> On Wed, Apr 19, 2023 at 11:03 AM Jan Høydahl < >>>>>>>>>>>> jan....@cominvent.com >>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> wrote: >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> Merged. >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> 19. apr. 2023 kl. 16:10 skrev Houston Putman < >>>>>>>>>>>> hous...@apache.org >>>>>>>>>>>>>> : >>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> I think that's a good one to include. >>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> - Houston >>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> On Wed, Apr 19, 2023 at 7:37 AM Jan Høydahl < >>>>>>>>>>>>> jan....@cominvent.com> >>>>>>>>>>>>>>>>>>>> wrote: >>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>> Is there still time to back-port >>>>>>>>>>>>>>>>>>>>>> https://issues.apache.org/jira/browse/SOLR-16755 >> ? >>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>> Jan >>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>> 12. apr. 2023 kl. 17:33 skrev Justin Sweeney < >>>>>>>>>>>>>>>>>>>> justin.sweene...@gmail.com >>>>>>>>>>>>>>>>>>>>>>> : >>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>> Awesome, thanks! I'll get that process started on >>>>> Monday, >>>>>>>>>>>> 4/17. >>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>> On Wed, Apr 12, 2023 at 11:31 AM Houston Putman < >>>>>>>>>>>>>>>>>> hous...@apache.org> >>>>>>>>>>>>>>>>>>>>>> wrote: >>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>> That'd be awesome, thanks! >>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>> No documentation really (and if you find any it >>> will >>>>> be >>>>>>>>> very >>>>>>>>>>>>>>>>>>>>>> out-of-date). >>>>>>>>>>>>>>>>>>>>>>>> The release process is all managed by the >> "release >>>>>>>> wizard" >>>>>>>>>>>> (a >>>>>>>>>>>>>>>>>>> million >>>>>>>>>>>>>>>>>>>>>>>> thanks to Jan). >>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>> So you can start it by: >>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>> 1. Check out the "branch_9_2" branch >>>>>>>>>>>>>>>>>>>>>>>> 2. (install python3/pip3 if you don't have them >>>>>>>> downloaded >>>>>>>>>>>>>>>>>> already) >>>>>>>>>>>>>>>>>>>>>>>> 3. pip3 install -r >>>> dev-tools/scripts/requirements.txt >>>>>>>>>>>>>>>>>>>>>>>> 4. ./dev-tools/scripts/releaseWizard.py --init >>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>> You can start/stop the wizard at any time, the >>> state >>>>> is >>>>>>>>>>>> saved. >>>>>>>>>>>>> I >>>>>>>>>>>>>>>>>>> would >>>>>>>>>>>>>>>>>>>>>>>> suggest that you do the entire release process >> on >>>> one >>>>>>>>>>>> computer >>>>>>>>>>>>>>>>>>> though, >>>>>>>>>>>>>>>>>>>>>>>> switching computers is very hard. >>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>> Also start the wizard before you want to >> actually >>> do >>>>> the >>>>>>>>>>>>> release. >>>>>>>>>>>>>>>>>>>> There >>>>>>>>>>>>>>>>>>>>>> are >>>>>>>>>>>>>>>>>>>>>>>> initial steps that are meant to be done days >>> before >>>>> the >>>>>>>>>>>> release >>>>>>>>>>>>>>>>>> is >>>>>>>>>>>>>>>>>>>>>> created. >>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>> There will be two particular snags since you >>> aren't >>>> a >>>>>> PMC >>>>>>>>>>>>> member, >>>>>>>>>>>>>>>>>>> but >>>>>>>>>>>>>>>>>>>>>> they >>>>>>>>>>>>>>>>>>>>>>>> will come up early and the releaseWizard will >>> prompt >>>>> you >>>>>>>> to >>>>>>>>>>>>>>>>>> address >>>>>>>>>>>>>>>>>>>>>> them. >>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>> If you have any questions, do not be afraid to >>> ask. >>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>> - Houston >>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>> On Wed, Apr 12, 2023 at 11:22 AM Justin Sweeney >> < >>>>>>>>>>>>>>>>>>>>>>>> justin.sweene...@gmail.com> >>>>>>>>>>>>>>>>>>>>>>>> wrote: >>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>> +1 If you need a volunteer to execute the >>> release, >>>> I >>>>>> can >>>>>>>>>>>>>>>>>> volunteer >>>>>>>>>>>>>>>>>>> to >>>>>>>>>>>>>>>>>>>>>> do >>>>>>>>>>>>>>>>>>>>>>>>> that next week. Are there docs available for >> the >>>>>> release >>>>>>>>>>>>>>>>>> process as >>>>>>>>>>>>>>>>>>>>>> it'd >>>>>>>>>>>>>>>>>>>>>>>> be >>>>>>>>>>>>>>>>>>>>>>>>> my first time through? >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>> Justin >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>> On Tue, Apr 11, 2023 at 12:10 PM Jan Høydahl < >>>>>>>>>>>>>>>>>>> jan....@cominvent.com> >>>>>>>>>>>>>>>>>>>>>>>>> wrote: >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>> +1 >>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>> Jan >>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>> 11. apr. 2023 kl. 15:51 skrev Houston Putman >> < >>>>>>>>>>>>>>>>>> hous...@apache.org >>>>>>>>>>>>>>>>>>>> : >>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>> Hello everyone, >>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>> I know we just released 9.2 around 2-3 weeks >>> ago, >>>>> but >>>>>>>> it >>>>>>>>>>>>> looks >>>>>>>>>>>>>>>>>>> like >>>>>>>>>>>>>>>>>>>>>>>> we >>>>>>>>>>>>>>>>>>>>>>>>>> are >>>>>>>>>>>>>>>>>>>>>>>>>>> going to need a bugfix release soon. >>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>> You can see the list of bugs here: >>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> >>>>>> https://issues.apache.org/jira/projects/SOLR/versions/12353017 >>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>> I think we should discuss starting the >> release >>>>>> process >>>>>>>>>>>> early >>>>>>>>>>>>>>>>>> next >>>>>>>>>>>>>>>>>>>>>>>> week, >>>>>>>>>>>>>>>>>>>>>>>>>> as >>>>>>>>>>>>>>>>>>>>>>>>>>> some of these bugs are pretty bad >> (Particularly >>>> the >>>>>>>> SSL >>>>>>>>> & >>>>>>>>>>>>>>>>>> HTTP2 >>>>>>>>>>>>>>>>>>>> bug - >>>>>>>>>>>>>>>>>>>>>>>>>>> SOLR-16728 < >>>>>>>>>>>>> https://issues.apache.org/jira/browse/SOLR-16728 >>>>>>>>>>>>>>>>>>> ). >>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>> - Houston >>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>> >>>> --------------------------------------------------------------------- >>>>>>>>>>>>>>>>>>>>>>>>>> To unsubscribe, e-mail: >>>>>>>> dev-unsubscr...@solr.apache.org >>>>>>>>>>>>>>>>>>>>>>>>>> For additional commands, e-mail: >>>>>>>>> dev-h...@solr.apache.org >>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>> >>>>>> >> --------------------------------------------------------------------- >>>>>>>>>>>>>>>>>>>>>> To unsubscribe, e-mail: >>>> dev-unsubscr...@solr.apache.org >>>>>>>>>>>>>>>>>>>>>> For additional commands, e-mail: >>>>> dev-h...@solr.apache.org >>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>> >>>> --------------------------------------------------------------------- >>>>>>>>>>>>>>>>>>>> To unsubscribe, e-mail: >>> dev-unsubscr...@solr.apache.org >>>>>>>>>>>>>>>>>>>> For additional commands, e-mail: >>>> dev-h...@solr.apache.org >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>> >>>> --------------------------------------------------------------------- >>>>>>>>>>>>>>> To unsubscribe, e-mail: dev-unsubscr...@solr.apache.org >>>>>>>>>>>>>>> For additional commands, e-mail: >> dev-h...@solr.apache.org >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>> >>>> --------------------------------------------------------------------- >>>>>>>>>>>>> To unsubscribe, e-mail: dev-unsubscr...@solr.apache.org >>>>>>>>>>>>> For additional commands, e-mail: dev-h...@solr.apache.org >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>> --------------------------------------------------------------------- >>>>>>>>> To unsubscribe, e-mail: dev-unsubscr...@solr.apache.org >>>>>>>>> For additional commands, e-mail: dev-h...@solr.apache.org >>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>> >>>>>> >>>>>> >> --------------------------------------------------------------------- >>>>>> To unsubscribe, e-mail: dev-unsubscr...@solr.apache.org >>>>>> For additional commands, e-mail: dev-h...@solr.apache.org >>>>>> >>>>>> >>>>> >>>> >>> >> --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@solr.apache.org For additional commands, e-mail: dev-h...@solr.apache.org
