Yep, RM is responsible for this, no wors. If you guys can wait until Sat/Sun 
I'll roll the RC...

Cheers,
Chris

On Apr 14, 2011, at 3:52 AM, Markus Jelsma wrote:

> Is the RM responsible for changing all 1.3-dev occurences to 1.3 such as in 
> pom, default.properties and http.agent name? The wiki states that updating 
> default.properties is part of releasing but what about -dev?
> 
> On Thursday 14 April 2011 09:55:32 Julien Nioche wrote:
>> There has been a large number of substantial changes with 1.3 (search
>> delegated to SOLR, separation between local and distributed runtimes, ....)
>> and we'll need to reflect this in the documentation the site and the wiki.
>> The good news is that a lot of this will be relevant for 2.0 as well.
>> 
>> BTW thanks for your work on cleaning up old issues on JIRA
>> 
>> On 13 April 2011 23:13, Markus Jelsma <[email protected]> wrote:
>>> Hi,
>>> 
>>> There are 4 open issue's for 1.3, 2 are already fixed in 1.3 of which 1
>>> is ready to commit for trunk the other is fixing license headers for
>>> trunk. Two
>>> very small issues remain which i can fix within the next few days.
>>> 
>>> Beyond that, i'll at least do a clean build and do a complete crawl with
>>> some
>>> plugins enabled do see if anything else goes wrong.
>>> 
>>> Whats's up next? I read Chris volunteers to manage the release, that
>>> would be
>>> great, but what else is there to do for 1.3?
>>> 
>>> Cheers,
> 
> -- 
> Markus Jelsma - CTO - Openindex
> http://www.linkedin.com/in/markus17
> 050-8536620 / 06-50258350


++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Chris Mattmann, Ph.D.
Senior Computer Scientist
NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
Office: 171-266B, Mailstop: 171-246
Email: [email protected]
WWW:   http://sunset.usc.edu/~mattmann/
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Adjunct Assistant Professor, Computer Science Department
University of Southern California, Los Angeles, CA 90089 USA
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Reply via email to