OK, they’re fixed in SVN but will take a few minutes to get propagate out to
the site. I’ll check in a little bit after dinner.
On Sep 22, 2021, 4:34 PM -0500, Cassandra Targett ,
wrote:
> Because when I tried to fix my initial mistake I only updated the HTML pages
> and thought I coul
ges are
> showing as broken links?
> https://solr.apache.org/guide/8_10/schema-designer.html ... the images
> are in images/schema-designer
>
> On Wed, Sep 22, 2021 at 2:31 PM Cassandra Targett
> wrote:
> >
> > I uploaded the 8.10 Ref Guide to https://solr.apache.or
I uploaded the 8.10 Ref Guide to https://solr.apache.org/guide/8_10/ in DRAFT
while we’re voting on the release.
I accidentally first uploaded a version of the Ref Guide built on `main` branch
back in March (a leftover from before the project split that didn’t get caught
with `ant clean`). I’m
; > gets a few test spins on main before the 8.9 release too. Whyt Mayya?
> >
> > Jan
> >
> > > 1. jun. 2021 kl. 23:04 skrev Cassandra Targett :
> > >
> > > I got a question this morning about some Jetty CVEs that look to be fixed
> > > with Je
I got a question this morning about some Jetty CVEs that look to be fixed with
Jetty 9.4.39, and there’s an issue marked as a Blocker (with no version) to
upgrade to that version. Is there time to do that for 8.9? Or is it too high
risk or would take too long?
in the 8x branch, but I didn't investigate further on
> how they would differ. Was just trying to be helpful and give you a heads up
> about it, but looks like I caused more confusion than help!
>
> > On Mon, Mar 29, 2021 at 1:31 PM Cassandra Targett
> > wrote:
> > >
I pushed up the URL changes I mentioned.
Not sure what you mean, Mike, by “gradle->ant translation”? The build process
is different in branch_8x but it’s documented in the how-to-contribute page in
the ref guide that talks about contributing and building, etc.
On Mar 29, 2021, 12:55 PM -0500,
You mentioned maybe re-publishing the Ref Guide in one of the issues, do you
still want to do that? If so, I should backport URL changes for the project
split (https://issues.apache.org/jira/browse/SOLR-15212) - it won’t be a
problem for me to do that before the end of this week.
On Mar 29,
For the Ref Guide a good amount of the traffic is probably the old redirect
rules in Confluence that explicitly went to 6_6 for a good reason *at the
time*. A blanket fix to those rules (it was a discrete list of pages in a text
file) to remove the URL in the path would cause them to be
At times in the past (maybe still) there have been lots of issues with a
released fix version which are marked as Open, Reopened, or Patch Available.
It’s just not a thing we monitor or correct very comprehensively so those
issues are very likely still open and should not be closed.
To be sure
I have a slightly different view - the thing that creates a paramset, stored in
a file called params.json, is called the Request Params API, primarily driven
by RequestParams.java, which is why the page is called that. The discrepancy
between the naming of the API and the thing it creates has
> > > >
> > > > > > I ran it twice on my old-ish MacBook, and it failed each time on
> > > > > > Solr tests that have a history of flakiness (as shown by Hossman's
> > > > > > awesome fucit.org site) -- AutoscalingHistoryHandle
I’ve updated the Ref Guide to remove the DRAFT status on 8.8 pages, so that’s
done. I’ll also take care of the next Ref Guide step to update the website to
show 8.8 as the latest.
On Jan 28, 2021, 9:59 AM -0600, Tomás Fernández Löbbe ,
wrote:
> It’s 9 binding: Noble, Tim, me, Ignacio, Mike M,
I’ve put up the DRAFT version of the Ref Guide for 8.8:
https://lucene.apache.org/solr/guide/8_8/.
I also created the Jenkins job for building the 8.8 guide which pushes to the
Nightlies server in case we have edits between now and release
gt; 14. jan. 2021 kl. 21:00 skrev Cassandra Targett :
> >
> > This is in the “how to publish the ref guide” docs [1], but not sure it’s
> > in any docs a RM follows, and I can’t remember if Atri pushed the final
> > version for the 8.7 release or if I did it and forgot thi
This is in the “how to publish the ref guide” docs [1], but not sure it’s in
any docs a RM follows, and I can’t remember if Atri pushed the final version
for the 8.7 release or if I did it and forgot this step.
At any rate, I’ll do it now just to fix it.
[1]
I’m really late to the party since I was offline for the weekend and catching
up yesterday, but the Draft Ref Guide for 8.7 is up (late):
https://lucene.apache.org/solr/guide/8_7/
I’ll update to the final version when it’s released, I should have plenty of
time for that in the back half of
Hi all -
I’m going to do a bit of moving of stuff around from the old Solr wiki so it’s
easier to get a sense for what content we may still care about. There are a
couple main things I’ll do (in the SOLR space only):
— Move pages with content that’s migrated to the Ref Guide to be a child of a
; SOLR-14835, but from the comments on the ticket it looks like it ended
> > > > up being purely a cosmetic issue. Andrzej left a comment there
> > > > suggesting that we "address" this with documentation for 8.6.3 but
> > > > otherwise leave it as-is.
>
If the old wiki page is old and out of date, just edit it to remove the old
content and point people who might find the old page to the Ref Guide page.
There’s no need for a Jira to edit the “old wiki”, just do it IMO. I mean,
who’s attached to that content? No one is editing a lot of it,
>
> > On Thu, Oct 15, 2020 at 5:16 PM Cassandra Targett
> > wrote:
> > > I updated the Ref Guide for 8.7 to include a link to the plugin repo (for
> > > all plugins which have an established repo, not just DIH), hoping that
> > > would help answer
I updated the Ref Guide for 8.7 to include a link to the plugin repo (for all
plugins which have an established repo, not just DIH), hoping that would help
answer user questions and spur adoption. That’s just a super-minor thing, but
it’s something.
If Rohit doesn’t have time to be a
Oops, I did some bad conflict resolution on a doc. Fixing.
On Oct 9, 2020, 12:10 PM -0500, Apache Jenkins Server
, wrote:
> Build:
> https://ci-builds.apache.org/job/Lucene/job/Solr-reference-guide-8.x/83/
>
> Log:
> Started by an SCM change
> Running as SYSTEM
> [EnvInject] - Loading node
> > > > push to it?
> > > >
> > > > so i creaed a GH issue w/patch...
> > > >
> > > > https://github.com/docker-solr/docker-solr/issues/349
> > > >
> > > >
> > > >
> > > > : Date: Tue
ended
> > up being purely a cosmetic issue. Andrzej left a comment there
> > suggesting that we "address" this with documentation for 8.6.3 but
> > otherwise leave it as-is.
> >
> > So it looks like we're unblocked on starting the release process.
> > Will b
It looks to me like everything for 8.6.3 is resolved now
(https://issues.apache.org/jira/projects/SOLR/versions/12348713), and it seems
from comments in SOLR-14897 and SOLR-14898 that those fixes make a Jetty
upgrade less compelling to try.
Are there any other issues not currently marked for
Atri,
Just so I understand your plans, when you say you are planning to start the
process at the end of this month, you mean you intend to create the branch
around Oct 1? No pressure, I ask only because Ishan’s original mail mentioned
cutting the branch this week and I just wanted to have a
There will be a “Major Changes in Solr 9” page in the Ref Guide for 9.0 that
can cover the removed features and available replacements in detail, which
similar pages have done for 6, 7, and 8 so far.
I don’t think a page dedicated to deprecated features makes sense beyond the
release when the
t says, I have access to:
> * lucene-site
> * lucene-solr
>
> So hopefully but the time I am ready to merge, I can. If not, I'll be back
> here.
>
> Thank you,
> Alex.
>
> On Fri, 28 Aug 2020 at 14:15, Cassandra Targett wrote:
> >
> > You do have to link you
You do have to link your GitHub and Apache identities. You need to have 2FA
enabled on your GH account.
Add your GH ID to your ASF LDAP profile at id.apache.org. It can take a couple
hours for you to be added to the Apache org in GitHub.
I think that’s all it takes, but you can go here to
Follow-up on this - we fixed the Solr Ref Guide builds last week, but there was
an outstanding issue which was the Content Security Policy on Cloudbees is too
stringent to display the Ref Guide’s CSS and JS. It blocked all the content
basically, rendering them unreadable.
Infra helped us
Later, we
> can get rid of "SolrCloud" and call it something else. Also, once SolrCloud
> is stable enough, we can get rid of legacy mode altogether. We can discuss
> that elsewhere.
>
> > On Tue, 11 Aug, 2020, 7:16 pm Cassandra Targett,
> > wrote:
&g
Cluster”, etc., as
appropriate.
Cassandra
On Aug 7, 2020, 9:05 AM -0500, Cassandra Targett , wrote:
> The suggestion to use “managed” and maybe “self-managed” is an interesting
> one. Do you think it’s possible some might confuse that with the other ways
> we use managed - like the “manag
;
> Same idea as coordinated vs uncoordinated basically. I don't know why but I
> prefer "managed".
>
> Ilan
>
> > On Thu, Aug 6, 2020 at 5:49 PM Cassandra Targett
> > wrote:
> > > On Aug 6, 2020, 10:22 AM -0500, Gus Heck , wrote:
> > > > WRT
been able to think of/find one.
I think it’s important to think about what differentiates the two ways of
managing a Solr cluster and derive the naming from that. What features of
SolrCloud don’t exist in the non-SolrCloud approach? What words help us
generalize those gaps and can any of them be an appro
, wrote:
> +1 Cassandra. These names are very appropriate. I'm glad we'll get rid of
> "SolrCloud" name.
>
> > On Thu, 6 Aug, 2020, 7:57 pm Cassandra Targett,
> > wrote:
> > > The work in SOLR-14702 has left us with some awkward phrasing (which is
> > &
The work in SOLR-14702 has left us with some awkward phrasing (which is
still better than what it was) around non-SolrCloud clusters that I've
offered to help fix.
I think we've struggled for years to find a good name for non-SolrCloud
clusters and we've used a number of variations: "legacy
I've pushed up the draft Solr Ref Guide for 8.6:
https://lucene.apache.org/solr/guide/8_6/.
This release will be the public debut of the redesign I finished a couple
months ago; if you have time, please explore around to find any issues I
may have missed.
On Wed, Jul 8, 2020 at 7:38 AM Noble
I’ll throw out the same suggestion I made when we had the same conversation
about 6 months ago - we should make a 9.0 Roadmap wiki page, use it to write
down & agree on goals, then add labels to Jira issues so we can go back to the
wiki page and add queries which automatically query Jira and
.
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > On 27 Jun 2020, at 04:59, Tomás Fernández Löbbe
> > > > &
I started looking at the Ref Guide for 8.6 to get it ready, and notice there
are no Upgrade Notes in `solr-upgrade-notes.adoc` for 8.6. Is it really true
that none are needed at all?
I’ll add what I usually do about new features/changes that maybe wouldn’t
normally make the old Upgrade Notes
I work at Lucidworks but not on that team, so take this with a grain of salt:
It seems they simply neglected to update the tags & compatibility table. There
is a 3.8.0 version of the .jar on Maven Central:
https://search.maven.org/artifact/com.lucidworks.spark/spark-solr/3.8.0/jar,
which if
e
>> are more easily reachable.
>> ~ David
>>
>>
>> On Thu, May 21, 2020 at 10:38 AM Cassandra Targett
>> wrote:
>>
>>> Yes, this is a known issue with Jira and the use of security levels.
>>> Atlassian (the maker of Jira) has known about it for ye
Yes, this is a known issue with Jira and the use of security levels.
Atlassian (the maker of Jira) has known about it for years and has not
fixed it yet.
This was last discussed about a year ago and that thread has an
explanation:
Agreed this is great and difficult work, Ilan. Thanks so much for taking it on.
I wonder if some of this maybe should end up in Javadocs? If those classes
don’t say what they’re doing or seem incomplete (and I have no idea what they
say about themselves) then we should consider maybe using some
; > > > > > > > >
> > > > > > > > > > > > > > > > > > > > On Fri, Apr 10, 2020 at 1:35 AM Marcus
> > >
Jan, I also see the same text you hoped to fix with SOLR-14359.
I think I might see a clue to the problem - in your PR you updated
“angular-chosen.min.js” but the head section of index.html also calls
“chosen.jquery.min.js”.
The problematic text in the drop downs is found in a element
Thanks for your message, Gus. You touched on things I was thinking this morning
as I caught up to the thread, and had started to draft a message about.
I feel like there is an assumption underlying some of our discussion about
packages that says a feature or whatever has to either part of our
Should we consider backporting SOLR-14367 (the most recent Tika upgrade)? It
addresses a CVE in Tika, and while I think we usually avoid changing 3rd party
component versions in patch releases, but maybe we should in this case? The
upgrade also looks like it was pretty straightforward (drop-in
w them. I can look into adding them to the release
> wizard as well.
>
> > On 16 Mar 2020, at 15:15, Cassandra Targett wrote:
> >
> > What do we need to do to get pushing the Ref Guide up as part of the RM
> > process? It’s super simple now, but I’m not sure what ne
What do we need to do to get pushing the Ref Guide up as part of the RM
process? It’s super simple now, but I’m not sure what needs to change to make
it happen regularly as part of release.
Cassandra
On Mar 16, 2020, 3:48 AM -0500, Alan Woodward , wrote:
> Let’s keep both pages as Draft for now
I pushed the Solr Ref Guide DRAFT up this morning (thought I did it on Friday,
sorry): https://lucene.apache.org/solr/guide/8_5/.
Cassandra
On Mar 15, 2020, 6:06 PM -0500, Uwe Schindler , wrote:
> Hi,
>
> I instructed Policeman Jenkins to automatically test the release for me, the
> result
:
>
> > On Tue, Mar 3, 2020 at 4:35 PM Cassandra Targett
> > wrote:
> > > The Release Notes (feature/improvement highlights) will still be in
> > > CWIKI, right (even if just for now)?
> >
> > Yes I think so. This really should be strictly a major highlights
I’m just finally getting around to looking at this to prep for 8.5. Thanks
David & Jan for working on this, I think it will help.
I have a few questions for this release:
The Release Notes (feature/improvement highlights) will still be in CWIKI,
right (even if just for now)?
Do we want to try
Yes, you’re correct.
We currently have only one screen used for create, edit, and view in each
project. To change which fields show in any one of those views, we need another
screen. Only Jira administrators can make a screen and update the screen scheme
to use it, and, for our Jira, only
Our Jira is connected to Confluence and supports some pretty nice integration
features. Instead of trying to organize 100s of issues in Jira, we could make a
"9.0 Planning" page in Confluence and use that integration to show us issue
status along our primary goals.
This integration is
Every year, the Lucene PMC rotates the Lucene PMC chair and Apache Vice
President position.
This year we have nominated and elected Anshum Gupta as the Chair, a
decision that the board approved in its January 2020 meeting.
Congratulations, Anshum!
Cassandra
Shoot, the issue is SOLR-12930, not what I wrote
earlier...https://issues.apache.org/jira/browse/SOLR-12930
On Jan 13, 2020, 3:25 PM -0600, Cassandra Targett ,
wrote:
> I’m hoping to resurrect this - I didn’t have time to help out with this last
> Summer, but I’m hoping I have some ti
I’m hoping to resurrect this - I didn’t have time to help out with this last
Summer, but I’m hoping I have some time now. There was an earlier conversation
about what to do with developer docs back in Oct 2018, so I’ve also updated
SOLR-12940 to use for creating the developer doc structure and
, 2019, 9:27 AM -0600, Cassandra Targett ,
wrote:
> These Ref Guide build failures are happening because apparently the rvm.io
> domain got parked when the certificate expired (today), and we use it to
> download the Ruby gems the build needs.
>
> The maintainer is working
These Ref Guide build failures are happening because apparently the rvm.io
domain got parked when the certificate expired (today), and we use it to
download the Ruby gems the build needs.
The maintainer is working on it
(https://twitter.com/mpapis/status/1211657656676618241) but it’s not clear
+1 to removing from CHANGES.txt, but I think we should really try to publish
them somewhere instead of asking people to look for .jars.
If we were to go the way I’ve been advocating to go - to have a single page in
the Ref Guide for each release that includes the new features + upgrade notes
A little late for some votes, but the Draft version of the 8.4 Solr Ref Guide
is up now: https://lucene.apache.org/solr/guide/8_4/
(I need to get on automating it soon.)
On Dec 18, 2019, 8:52 AM -0600, Gus Heck , wrote:
> Hi Mkhail, This is a known flakey test (mine, it's on my to do list).
I’m going to have a few commits coming in to branch_8_4 today for the Ref Guide
- I’m assuming as usual it’s OK for me to go ahead but if you want me to hold
for a short time while you’re building or whatever, I will.
On Dec 16, 2019, 9:35 AM -0600, Adrien Grand , wrote:
> Awesome, thanks Ishan.
The license .sha file was already updated, the right version just wasn’t in
that build.gradle. Sorry again for the added noise, merging is messy ;-).
Cassandra
On Nov 13, 2019, 7:47 AM -0600, Cassandra Targett ,
wrote:
> Yes, Erick, that was the cause of the problem Dawid noticed - I j
le and ant builds
> successfully.
>
> WDYT about just checking this in to the gradle_8 branch so we can all iterate
> from the same base? Who knows? Maybe whatever makes me “special” will be
> obvious.
>
> Oh, and now you know why people don’t trust me to make hardware chan
I’ll look into it now.
Cassandra
On Nov 12, 2019, 4:09 PM -0600, Dawid Weiss , wrote:
> Hi Cassandra,
>
> I fixed relative links issue (on jira/SOLR-13452_gradle_8) but there's
> still something odd with asciidoctor -- while the html site generation
> is fine now the validation isn't:
>
>
I was able to get the changes Dawid and I worked out in the gradle_7_refguide
branch merged into the gradle_8 branch.
There’s one current problem with it, which may be something in my env: in the
grade_7_refguide branch the HTML files were generated in
./solr/solr-ref-guide/build, but now they
PM Adrien Grand wrote:
> > I'd be fine with option 2 but I have a slight preference for option 3.
> > If we see the Gradle build as the future default build, then we need
> > to start using it and I wonder that having to use a different workflow
> > on branch_8x would be an i
I’m fine with Option 2.
Putting my project manager hat on, I’d really like to see a central list or
Jira issues of the things we want to make sure to do before we can turn off
Ant. The list/sub-tasks could be compiled after it’s merged to master, but it
would be nice if we could approach this
g adoc. Try it :)
>
> --
> Jan Høydahl, search solution architect
> Cominvent AS - www.cominvent.com
>
> > 6. nov. 2019 kl. 21:32 skrev Cassandra Targett :
> >
> > I was far too swamped back in July to be able to take a look at this new
> > tool, but I’v
I was far too swamped back in July to be able to take a look at this new tool,
but I’ve had a few minutes now and while I’ve never done a release, it really
looks very helpful.
Jan, I note in your initial description in this thread and in LUCENE-8852 you
mention the release wizard tool allows
We’re still working out the changes to the publication process, and got a
couple wires crossed that prevented the Ref Guide from being published at the
same time for this release.
I’ve published the final version now: http://lucene.apache.org/solr/guide/8_3/.
Apologies for the confusion, by
Yes, it does need to be updated. I was waiting to do that until I informed the
user list about the change to not publish a PDF any longer which I’m ready to
send now, so I’ll also fix the redirect link.
Cassandra
On Oct 28, 2019, 12:23 PM -0500, Gus Heck , wrote:
> Ah yes I assumed that the
t 3:46 PM Cassandra Targett
> wrote:
> >
> > Thanks everyone, by the way, for the encouragement and feedback here.
> >
> > For next steps, how do folks feel about making the change to stop voting on
> > the PDF *now*? Or, I guess, retroactively for 8.2 since that
Since we’re only sort of half-way through revamping the Solr Ref Guide release
process, I’ve manually pushed up the 8.3 Ref Guide with a DRAFT watermark if
anyone would like to review it while looking at the packages:
https://lucene.apache.org/solr/guide/8_3/.
Cassandra
On Oct 21, 2019, 2:17
On Oct 19, 2019, 1:32 PM -0500, Ishan Chattopadhyaya
, wrote:
> Thanks a lot Andrzej and Shalin.
> I'll try to build the RC on Monday. FYI, upon Jan's advice, I'll be using his
> release wizard tool. Also, I'll need to dig into the simultaneous refguide
> release situation. So, i might need
On Oct 17, 2019, 11:03 AM -0500, Dawid Weiss , wrote:
> > I’m not sure the next steps here - we could merge the changed files into
> > the main Gradle branch?
>
> I'm kind of waiting for Mark to coordinate this, actually. I've
> modified some test code on the gradle branch but Mark has been
o work. Please feel free to upgrade to newer versions
> > of those tools -- if it works we should be using newer, supported
> > version lines I think.
> >
> > Dawid
> >
> > On Fri, Oct 11, 2019 at 10:20 PM Cassandra Targett
> > wrote:
> > >
>
Done, Ishan, thanks!
Cassandra
On Oct 16, 2019, 2:37 PM -0500, Ishan Chattopadhyaya
, wrote:
> +1, Cassandra! Thanks.
>
> > On Wed, 16 Oct, 2019, 11:41 PM Cassandra Targett,
> > wrote:
> > > Sorry, I meant branch_8_3.
> > >
> > > Cassandra
>
If you build the Ref Guide HTML files on your local machine, please note
the following changes to the build.
To build the Ref Guide HTML version locally, you must have several Ruby
gems installed as pre-requisites. I've just committed changes that require
newer versions of these gems.
You can
I pushed a fix for this and it’s fine now.
Cassandra
On Oct 16, 2019, 12:05 PM -0500, Apache Jenkins Server
, wrote:
> Build: https://builds.apache.org/job/Solr-reference-guide-master/19516/
>
> Log:
> Started by timer
> Running as SYSTEM
> [EnvInject] - Loading node environment variables.
>
>
> Sure. Try and see if you can make it work. It is just about the only thing
> that still needs to be done, the rest works like a charm.
>
> > On Fri, Oct 11, 2019, 20:20 Cassandra Targett wrote:
> > > Sorry for the delay getting back to you Dawid. That problem is actuall
the future. The initial step would be probably to get
> > > the site generation running on Linux/ Macs but I'd gladly hand it over
> > > back to you -- I can help with Gradle but a the rest of those tools
> > > are a mistery to me.
> > >
> > > Dawid
> >
Thanks Dawid for working on this! I’ve been a bit swamped the last couple of
days but will take a look today at what you’ve been able to do so far and see
where we might need to go from here.
Cassandra
On Sep 26, 2019, 7:25 AM -0500, Dawid Weiss , wrote:
> I agree. Although I also understand
I just pushed a new branch for the Ref Guide based off the gradle_7 branch
(it’s "jira/SOLR-13452_gradle_7_refguide”). I’m completely stuck and try as I
might I can't get myself unstuck with the time I have.
There are several phases to our current build, and some of these we can drop if
we
lan
>
> On Thu, Sep 19, 2019 at 11:57 PM Cassandra Targett
> wrote:
> >
> > The pages do already have a “Site last generated” date on them at the
> > bottom. It’s specifically worded that way for a reason.
> >
> > We actually wanted the date the .adoc file
The pages do already have a “Site last generated” date on them at the bottom.
It’s specifically worded that way for a reason.
We actually wanted the date the .adoc file was last updated to be in the footer
too, but the problem has always been that a static site generator always
regenerates all
Sort of playing devil’s advocate for sake of discussion, why would we pick
Pelican static site generator over Jekyll static site generator which we
already use for the Ref Guide? Why would we stay with Markdown when we already
know that Asciidoc is a much more expressive markup language that we
The delays getting the Ref Guides for 8.x releases out have caused me to
think a bit about the Ref Guide publication process. It seems clear others
aren't able to pick up the process when I can't and I’m sure there are a
million individual reasons for that so I don't intend to shame or blame
As I’ve mentioned to some of you over the past couple of weeks, I want to
propose that we don’t “release” the Ref Guide at all the way we have been doing
it.
It deserves a separate thread, which since it’s come up a few times this week I
should start now, but in essence, my idea is to no
[v ] Leave it as is - I like quiet
I like the clear separation between the lists. It already feels less
hectic/overwhelming to me. I will read both as often as I can anyway, so I
don’t feel I’ll miss anything if the lists stay the way they are now.
There is a Jira plugin to support email
I got started on the Ref Guide build last night. The biggest change there is to
use the asciidoctor-gradle-plugin instead of using the asciidoctor-ant plugin.
So far I’ve got it working enough to build a single page of the Ref Guide into
a PDF file. Baby steps ;)
By itself that only gets us
[
https://issues.apache.org/jira/browse/SOLR-13714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Cassandra Targett resolved SOLR-13714.
--
Fix Version/s: 8.2
Assignee: Cassandra Targett
Resolution: Fixed
There are 7 resolved/closed issues with the fixVersion 8.1.2. Since that
version was never released, it’s misleading to leave only a fixVersion that was
never released. We know we can assume 8.2, but the average user may not.
Shouldn’t these all be changed to 8.2?
Cassandra
[
https://issues.apache.org/jira/browse/SOLR-13452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16909061#comment-16909061
]
Cassandra Targett commented on SOLR-13452:
--
For the docs, there is a plugin for Gradle from
[
https://issues.apache.org/jira/browse/SOLR-13523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16897597#comment-16897597
]
Cassandra Targett commented on SOLR-13523:
--
Since 8.1.2 was never released, should
[
https://issues.apache.org/jira/browse/SOLR-9162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Cassandra Targett closed SOLR-9162.
---
> Connection pool shut down
> -
>
> Ke
[
https://issues.apache.org/jira/browse/SOLR-9162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Cassandra Targett resolved SOLR-9162.
-
Resolution: Invalid
Closing as this should have gone to solr-user list first
[
https://issues.apache.org/jira/browse/SOLR-5467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16890171#comment-16890171
]
Cassandra Targett commented on SOLR-5467:
-
Yes, there are asciidoctor tools to convert the .adoc
1 - 100 of 1944 matches
Mail list logo
