[ 
https://issues.apache.org/jira/browse/SOLR-3786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13448145#comment-13448145
 ] 

Hoss Man commented on SOLR-3786:
--------------------------------

1) the README.txt file included in the BETA is static -- we can't retroactively 
change a release

2) Any user who upgrades to the ALPHA or BETA (or final) with their existing 
3.x configs will not be affected by this bug, because any pre-4 configs 
wouldn't have had updateLog in them -- so it does not make sense to mention 
this in "Upgrading from 3.6"  (if users try to combine an existing schema.xml 
with the new example solrconfig.xml, then all bets are off that anything will 
work -- i'm pretty sure that's been a recipe for disaster in every version of 
solr i can think of, because the examl solrconfig.xml has also refered to the 
fields in the example schema, and those change with each release.)

any user who upgrades to ALPHA or BETA and uses the new example configs would 
not be affected by this bug, because they have \_version_\ in them.

3) the wiki is a wiki, if you'd like to add  an errata for the 4.0-ALPHA/BETA 
releases and put this in it you are welcome to do so -- but frankly i don't 
think it makes sense to even have errata sections for those releases since they 
are ALPHA/BETA.  4.0-final is a diff story.
                
> upload log without a version causes updates to silently fail.
> -------------------------------------------------------------
>
>                 Key: SOLR-3786
>                 URL: https://issues.apache.org/jira/browse/SOLR-3786
>             Project: Solr
>          Issue Type: Bug
>          Components: update
>    Affects Versions: 4.0-BETA
>            Reporter: Dan Foley
>            Priority: Blocker
>
> Same as the following bug that should have been resolved in 4.0 beta.. 
> however i just loaded a fresh copy of 4.0 beta and the bug is still there.
> https://issues.apache.org/jira/browse/SOLR-3746

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to