lucenenet-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Shad Storhaug <>
Subject RE: JIRA and API Docs
Date Mon, 14 Oct 2019 09:36:49 GMT
I was looking into how that worked some time back and it seems the .cgi file contains the functionality
to switch between download mirrors + templates for customizing the layout. Technically, we
shouldn't be linking to because we are supposed to remove the
files from there after they are cached by the download mirrors. And the .cgi is setup to default
to the closest download mirror to the user, etc. One thing that occurred to me was that it
might be possible to use the .cgi as a sort of "web api" just to get the download mirror list,
and then use JavaScript to make a static HTML download page dynamic on an entirely different

I don't know much about .cgi. Is there a chance that we can just transfer those files over
to the current host and get them working? Or would a better option be to try to get the old
website live (on another domain perhaps?) so we can utilize it there?

-----Original Message-----
From: Shannon Deminick <> 
Sent: Monday, October 14, 2019 2:18 PM
Subject: Re: JIRA and API Docs

If we could have the old docs for both 3.0.3 and 2.9.4 hosted like they used to be on their
servers - so that things like download.cgi still worked, that would be great. But to have
only these docs hosted on another server on the same domain as the current site (i.e. + that would mean we'd probably have to have
some html page redirects to another (new) sub domain like ?

Otherwise, I could put the old static docs in the docs repo/site so they would just be hosted
there. Would mean I'd need to change the links for the download.cgi page and update that page
to be static like we have now.

On Mon, Oct 14, 2019 at 5:10 PM Shad Storhaug <> wrote:

> New INFRA ticket opened about gaining write access to lucenenet-site repo:
> -----Original Message-----
> From: Shad Storhaug <>
> Sent: Monday, October 14, 2019 12:45 PM
> To:
> Subject: RE: JIRA and API Docs
> Shannon,
> I found the ticket that was opened to create the web site and asked 
> infra about this, and it seems the docs are still available in SVN:
> ent/
> I will open another ticket to get access to the lucenenet-site repo 
> (for both you and me) so we can deploy the web site.
> I am not sure if it will be possible to keep both the temp site you 
> have the docs hosted on and the old URLs of the API docs, though. I 
> suppose we could aim to put them on the permanent domain now so we 
> don't have to update the lucenenet README and other places that are 
> linking to the legacy docs. Are there any issues preventing that from happening?
> Thanks,
> Shad Storhaug (NightOwl888)
> -----Original Message-----
> From: Shannon Deminick <>
> Sent: Monday, October 14, 2019 12:17 PM
> To:
> Subject: Re: JIRA and API Docs
> Hi, yes I suppose this was a side effect of transferring to the new 
> website. It was some time ago now so I can't recall if we had thought 
> about this or not ... but it certainly seems like an oversight on my 
> part :(
> There are some references to these sites on if 
> all else fails could try to download the originals from there. 
> Otherwise could attempt to regenerate them all from source.
> Can we ask infra if the files still exist someplace?
> On Sun, Oct 13, 2019 at 8:38 PM Shad Storhaug <>
> wrote:
> > Mladen,
> >
> > Thanks for the report. I wasn't aware of either of these issues.
> >
> > For JIRA, if I recall correctly when you create the login, it 
> > doesn't actually take you to the LUCENENET project. In order to get 
> > there you have to either do a JIRA search for it, go to the URL from 
> > a google search for LUCENENET issues, or you could go back and click 
> > the link again from the GitHub page after you create the login. 
> > Could you verify that you can create an issue by navigating to 
> > directly?
> >
> > For the legacy docs, @Shannon and @Laimonas, was this a side effect 
> > of the web site release or was it something INFRA did since the 
> > website was released?
> >
> > We do want to make sure legacy API docs for every version (including
> > pre-releases) are kept around for users of those versions by 
> > releasing to a versioned subdirectory and never deleting them. This 
> > is how Lucene does it, and how we should be doing it.
> >
> > Either way, does anyone know where the files for the legacy API docs 
> > sites are in case INFRA didn't save a copy?
> >
> >
> > Regards,
> > Shad Storhaug (NightOwl888)
> > Project Chairperson - Lucene.NET
> >
> > -----Original Message-----
> > From: Mladen Mihajlovic <>
> > Sent: Sunday, October 13, 2019 12:01 AM
> > To:
> > Subject: hard
> >
> > Wow it's hard to communicate with anybody about this project. The 
> > website points to github for source, which has no issue tracker 
> > enabled, but tells you to go to jira and make a login, which I did 
> > but then there is no way from there to actually make an issue.
> >
> > I really just wanted to log an issue that all the docs are missing 
> > for pre version 4. The links on the website are dead...
> >
> > cheers,
> > mladen
> >
> --
> Kind regards / Med venlig hilsen
> Shannon Deminick
> Phone: +45 70 26 11 62


Kind regards / Med venlig hilsen

Shannon Deminick

Phone: +45 70 26 11 62
View raw message