Thanks for the help! The link was an internal documentation I assumed it
was correct. I've updated it in our wiki page.
On Mon, Oct 28, 2019 at 7:57 PM Cassandra Targett
wrote:
> Yes, it does need to be updated. I was waiting to do that until I informed
> the user list about the change to not
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
Ah yes I assumed that the original link had come from a good source... OTOH
https://lucene.apache.org/solr/guide/field-types-included-with-solr.html still
needs to be updated to point to 8_2 I think.
On Mon, Oct 28, 2019 at 1:01 PM Chris Hostetter
wrote:
>
> : The redirection is wrong, if you
: The redirection is wrong, if you remove "latest" from the urls with 8_1 in
The "redirection" rules appear to be working as designed -- but AFAIK they
were never designed with any idea of having a "latest/" path.
the Latest URL has no is just the page name w/o a version number, not the
page
The redirection is wrong, if you remove "latest" from the urls with 8_1 in
them it looks like you get the right page. Also, 8_2 is the latest now so
these are also out of date I think.
On Mon, Oct 28, 2019 at 10:24 AM Gézapeti wrote:
> Hi everyone,
>
> I was trying to access
>
Hi everyone,
I was trying to access
https://lucene.apache.org/solr/guide/latest/field-types-included-with-solr.html
and it got redirected to
https://lucene.apache.org/solr/guide/8_1/latest/field-types-included-with-solr.html
which is a 404.
I've tested https://lucene.apache.org/solr/guide/latest/
FYI, bumping this - I’m about to send a mail to the user list explaining why
we’ve stopped releasing the PDF.
I think I said originally we’d publish the 8.2 PDF, but I’ve changed my mind on
that and edited the Ref Guide landing page to include 8.2 and indicate it is
HTML only starting with
+1. That all sounds good to me. Excited to see some streamlining here.
On Fri, Sep 20, 2019 at 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
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’s not out yet. I could
push the HTML and make a PDF but announce to the list that from
First of all a big thanks to Cassandra to help coordinate and build
our ref guide to make it professional. It really used to be pathetic
before you took over
. Yes we need to avoid "creating work" . There should be no need for a
ref guide release.
+1 for your plan
On Thu, Sep 19, 2019 at 11:57
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
I agree that we should be able to fix mistakes, my only suggestion was that
those mistakes not be non-trivial. But the more I think about it, the more
I feel convinced about just publishing the updates - however, having a time
stamp on when the guide was last updated would be nice to have.
Overall the direction here sounds good to me. I have/use the PDFs but
lately less so since I'm more and more simply searching the asciidoc files
within my IDE and viewing them nicely with the IDE plugin simultaneously.
~ David Smiley
Apache Lucene/Solr Search Developer
: > However Anshum does make a good point that users wouldn't know when
: the pages have changed. I think it would be great to have a link on each
: ref-guide page that shows the last modified date and links to the
: history of that page in github
: Perhaps we could instead provide a single
> However Anshum does make a good point that users wouldn't know when the pages
> have changed. I think it would be great to have a link on each ref-guide page
> that shows the last modified date and links to the history of that page in
> github
We now have an "Errata" page, which is never
I've had issues with asiidoc features available for the HTML version that
didn't work in PDF, and it was pretty frustrating to work around it. I
think just having the site would be an improvement for the development
side, but I've never used the PDF version myself.
Easy back-porting of
+1 to skip pdf and auto publish ref guides to html on every merge to a branch.
We could also start publishing a draft 9.x guide there, clearly labeled as work
in progress.
Jan Høydahl
> 18. sep. 2019 kl. 19:38 skrev Chris Hostetter :
>
>
> First and foremost I should mention: I'm currently
First and foremost I should mention: I'm currently in favor of just about
everything Cassandra has suggested here...
: So, I propose making some radical changes. My ideas here require a shift
: from thinking of the Guide as a release artifact like the binaries to
: thinking of it similar to
Thank you Cassandra for all of your effort so far.
I just love that idea. As I said in my previous email (based on my
discussion with Cassandra at Activate), having 2 processes, releases, one
of which almost the responsibility of one person doesn't sound reasonable.
It would also be great to get
+1 to automate... I never use the PDF I'd be happy to loose it. The page
count is the best part of the PDF :).
As far as indexing the ref guide... Cassandra gave a talk on that last
year...
https://www.youtube.com/watch?v=DixlnxAk08s=PLU6n9Voqu_1HW8-VavVMa9lP8-oF8Oh5t=14
On Wed, Sep 18, 2019 at
+1 on the suggested process. +1 on PDF just being too big, though it
is fun to quote the page count.
An additional idea piggy-backing on this is that in step 4, we could
also automatically build a local example/index that links to the
public version. So, people could search the guide locally and
21 matches
Mail list logo
