I updated http://lucene.staging.apache.org/solr/community.html <http://lucene.staging.apache.org/solr/community.html> with a table.
However, stepping back, it feels a bit mal-placed on a “Community” page. I wonder if we better move the version table or perhaps the whole explanation altogheter to a new solr/downloads.html page. Then we could move all text from http://lucene.staging.apache.org/solr/mirrors-solr-latest-redir.html <http://lucene.staging.apache.org/solr/mirrors-solr-latest-redir.html> to that page. To be honest, it’s a pain that our “Download” page is displayed for a few seconds only before redirecting. If we create a stable download.html page that page could have a table with links directly to the versions, the version specific ref-guides as well as info about CVE’s or documentation addendums etc. -- Jan Høydahl, search solution architect Cominvent AS - www.cominvent.com > 13. jan. 2017 kl. 01.56 skrev Walter Underwood <wun...@wunderwood.org>: > > I like the list version. Might want to use historical version numbers (4, 5, > 6) to > avoid predicting the future. We’re jumping from 4.10.4 to 6.4 right now. Well, > we have some 3.x in production, but I’m trying to stomp that flat. > > wunder > Walter Underwood > wun...@wunderwood.org <mailto:wun...@wunderwood.org> > http://observer.wunderwood.org/ (my blog) > > >> On Jan 12, 2017, at 4:12 PM, Shawn Heisey <apa...@elyograg.org >> <mailto:apa...@elyograg.org>> wrote: >> >> On 1/12/2017 3:36 PM, Jan Høydahl wrote: >>> I don’t like putting version numbers into the website, since they WILL >>> be out of date at some point. But it is hard to explain three >>> generations without giving examples, suggestions for how to avoid it? >> >> In the paragraph, don't mention the actual version numbers. Instead, >> refer to general version categories, and include something that's >> table-like where actual version numbers are given. Here's an example of >> what that table structure might contain, feel free to bikeshed as necessary: >> >> 5.5.x : Version in the previous major release for bugfixes >> 6.x : Current major version, comes from the stable branch_6x >> 7.0 : Next major version, will come from master branch >> >> When a new stable branch is built and we go looking for info that needs >> updating, this page will contain it all in one place. If the code that >> builds the website allows tags/comments that become invisible, perhaps >> we can come up with a way to tag this with a string that we can search >> for later when we we build a new stable branch. >> >> Thanks, >> Shawn >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org >> <mailto:dev-unsubscr...@lucene.apache.org> >> For additional commands, e-mail: dev-h...@lucene.apache.org >> <mailto:dev-h...@lucene.apache.org> >> >