Plus it looks like your SIS-35 updates might be missing too (from
NOTICE.txt and LICENSE.txt).  Maybe just needs a rebuild/merge to grab
the latest changes...


On 16 July 2012 13:01, Ross Laidlaw <[email protected]> wrote:
> Hi Chris,
>
> I think the sis-parent/pom.xml file in the 0.2-incubating-rc2 package
> is a different version (without patch for SIS-34) to the one in the
> 0.2-incubating branch.  So I think it needs to be updated/merged in
> order for the SIS-34 bug fix to be included in the release.
>
>
> Ross
>
>
>
> On 16 July 2012 01:23, Mattmann, Chris A (388J)
> <[email protected]> wrote:
>> Hi Folks,
>>
>> A candidate for the Apache SIS 0.2-incubating release is available at:
>>
>> http://people.apache.org/~mattmann/apache-sis-0.2-incubating/rc2/
>>
>> The release candidate is a tar.gz archive of the sources in:
>>
>>  http://svn.apache.org/repos/asf/incubator/sis/tags/0.2-incubating-rc2
>>
>> The SHA1 checksum of the archive is 6e9e6ef14b6d3fbcad8d17f74f7d637480e2a458.
>>
>> A staged Maven repository for Apache SIS is here:
>>
>> https://repository.apache.org/content/repositories/orgapachesis-052/
>>
>> Please vote on releasing this package as Apache SIS 0.2-incubating.
>> The vote is open for at least the next 72 hours and passes if a majority of 
>> at
>> least three +1 SIS PPMC votes are cast.
>>
>>  [ ] +1 Release this package as Apache SIS 0.2-incubating
>>  [ ] -1 Do not release this package because...
>>
>> Thanks!
>>
>> Cheers,
>> Chris
>>
>> P.S. Here's my +1.
>>
>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>> 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