[ https://issues.apache.org/jira/browse/SOLR-13256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16771382#comment-16771382 ]
Jason Gerlowski commented on SOLR-13256: ---------------------------------------- bq. Maybe it makes sense to hold the 7.7 Ref Guide until we figure out what is going to happen with those issues re: 7.7.1? I think that makes sense. If there is going to be a 7.7.1 soon that we're going to be steering everyone towards anyways, there's no need to include this in the ref-guide. If no one volunteers to do a 7.7.1 release soon and people are going to be using 7.7.0, then we can cross that bridge when we come to it. ---- (Thoughts below are only relevant if there is no 7.7.1 soon, and we need to cross the bridge of deciding whether to include Known Issues in our Upgrade Notes) bq. to date, we haven't mentioned Known Issues in the Upgrade Notes ... [this is] actually really hard for Solr ... What's the criteria for being included here? What about all the prior releases? I'm not sure the slope is as slippery as it looks. Yes, there are 1500 unresolved Solr bugs, but only 8 specifically tagged as affecting 7.7. And only 2 of those are being talked about as serious enough to trigger a bugfix release. The number of "candidates-for-inclusion" drops to just a few pretty quickly. If that's not convincing and your question about having guidelines/criteria wasn't rhetorical, let me offer a strawman for discussion: "Known Issues should only be included in the Upgrade Notes if they are generating discussion about an immediate bugfix release at the time the ref-guide release is being worked on". > Ref Guide: Upgrade Notes for 7.7 > -------------------------------- > > Key: SOLR-13256 > URL: https://issues.apache.org/jira/browse/SOLR-13256 > Project: Solr > Issue Type: Improvement > Security Level: Public(Default Security Level. Issues are Public) > Components: documentation > Reporter: Jason Gerlowski > Assignee: Jason Gerlowski > Priority: Major > Attachments: SOLR-13256.patch > > > With 7.7 released and out the door, we should get the ball moving on a 7.7 > ref-guide. One of the prerequisites for that process is putting together > some upgrade notes that can go in > {{solr/solr-ref-guide/src/solr-upgrade-notes.adoc}} for users upgrading to > 7.7. > I'm going to take a look at CHANGES and take a first pass at the "upgrading" > section for 7.7. If anyone has anything they know should be in the list, > please let me know and I'll try to include it. -- This message was sent by Atlassian JIRA (v7.6.3#76005) --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org