Cool - you probably also want to move another entry under that? Usually I've 
been using Additional Changes: below for this:

* SOLR-4543: setting shardHandlerFactory in solr.xml/solr.properties does not 
work.
  (Ryan Ernst, Robert Muir via Erick Erickson)

That's not a released bug right? If not we don't want it to appear so - we 
still want to give credit and have the tracking for trunk users I think, that's 
why I use the Additional Changes for follow on JIRAs to large CHANGES.

- Mark

On Mar 15, 2013, at 9:08 AM, Erick Erickson <[email protected]> wrote:

> Added some bits to CHANGES.txt for SOLR-4196....
> 
> 
> On Thu, Mar 14, 2013 at 10:01 PM, Erick Erickson <[email protected]> 
> wrote:
> OK, I'll see what I can put in tomorrow. It won't be comprehensive, probably 
> just refer to the Wiki page after a very brief explanation.
> 
> 
> On Thu, Mar 14, 2013 at 9:45 PM, Mark Miller <[email protected]> wrote:
> Okay - leaving it out on purpose can get kind of confusing - someone that 
> wanted to look at the state of trunk right now might think, oh, only bug 
> fixes and very minor changes, but surprise, there is actually a major 
> structural change.
> 
> I think we should try and keep CHANGES up to date with reality for our 
> 'trunk', '4x' users.
> 
> - Mark
> 
> On Mar 14, 2013, at 9:24 PM, Erick Erickson <[email protected]> wrote:
> 
> > bq: Is there any mention of this in CHANGES yet
> >
> > Nope, it's one of the JIRAs I've assigned to myself. SOLR-4542. I have 
> > started a Wiki page here:
> > http://wiki.apache.org/solr/Core%20Discovery%20%284.3%20and%20beyond%29
> >
> > linked to from here:
> > http://wiki.apache.org/solr/CoreAdmin#Configuration
> >
> > But I've been waiting for the dust to settle before fleshing this out much. 
> > Although the more exposure it gets, I suppose the more chance people will 
> > have to comment on it. If we're agreed that solr.properties is the way to 
> > go, then I'll put something in CHANGES Real Soon Now and perhaps let the 
> > Wiki page evolve in fits and starts.
> >
> >
> >
> > On Thu, Mar 14, 2013 at 8:43 PM, Mark Miller <[email protected]> wrote:
> > Is there any mention of this in CHANGES yet erick? Was just browsing for it…
> >
> > - Mark
> >
> > On Mar 14, 2013, at 6:37 PM, Jan Høydahl <[email protected]> wrote:
> >
> > > solr.yml :-)
> > >
> > > --
> > > Jan Høydahl, search solution architect
> > > Cominvent AS - www.cominvent.com
> > > Solr Training - www.solrtraining.com
> > >
> > > 14. mars 2013 kl. 22:02 skrev Yonik Seeley <[email protected]>:
> > >
> > >> On Thu, Mar 14, 2013 at 3:46 PM, Robert Muir <[email protected]> wrote:
> > >>> It seems to me there are two changes involved:
> > >>> 1. ability to auto-discover cores from the filesystem so you don't
> > >>> need to explicitly list them
> > >>> 2. changing .xml format to .properties
> > >>
> > >> These are indeed completely independent.
> > >> My main concern/goal in this area has been #1.
> > >> I assume #2 is just because developer tastes have been shifting away
> > >> from XML, but like you I worry about what happens for config that
> > >> needs more structure.
> > >>
> > >> -Yonik
> > >> http://lucidworks.com
> > >>
> > >> ---------------------------------------------------------------------
> > >> To unsubscribe, e-mail: [email protected]
> > >> For additional commands, e-mail: [email protected]
> > >>
> > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: [email protected]
> > > For additional commands, e-mail: [email protected]
> > >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [email protected]
> > For additional commands, e-mail: [email protected]
> >
> >
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
> 
> 
> 


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

Reply via email to