On Mon, May 11, 2009 at 1:45 PM, sebb wrote:
> On 11/05/2009, Christian Grobmeier wrote:
>> Hi all,
>>
>> as already discussed, I just created a RC1 for the first [compress] release
>> :-)
>> Let me know if you can find any problems.
>>
>> Cheers,
>> Christian
>>
>>
>> Tag:
>>
>> https://
On 12/05/2009, Jörg Schaible wrote:
> sebb wrote at Dienstag, 12. Mai 2009 13:47:
>
>
> > On 12/05/2009, Jörg Schaible wrote:
> >> sebb wrote at Dienstag, 12. Mai 2009 11:22:
> >>
> >> [snip]
> >>
> >>
> >> > One other change needed to SVN:
> >> >
> >> > svn ps svn:eol-style native
>
sebb wrote at Dienstag, 12. Mai 2009 13:47:
> On 12/05/2009, Jörg Schaible wrote:
>> sebb wrote at Dienstag, 12. Mai 2009 11:22:
>>
>> [snip]
>>
>>
>> > One other change needed to SVN:
>> >
>> > svn ps svn:eol-style native
>> >
src/main/java/org/apache/commons/compress/changes/ChangeSetResul
On 12/05/2009, Christian Grobmeier wrote:
> >> > Yes, I know; the original instructions (shown as outdated, at the
> >> > bottom) imply that it is possible; seems to me it would be a lot
> >> > better.
> >>
> >>
> >> No its not outdated - just the last paragraph is outdated by the above
>
>> > Yes, I know; the original instructions (shown as outdated, at the
>> > bottom) imply that it is possible; seems to me it would be a lot
>> > better.
>>
>>
>> No its not outdated - just the last paragraph is outdated by the above
>> writings:
>
> That's what I meant - the last para is marke
On 12/05/2009, Christian Grobmeier wrote:
> >> I think similar, but this has been done automatically when following:
> >> http://wiki.apache.org/commons/CreatingReleases
> >
> > Yes, I know; the original instructions (shown as outdated, at the
> > bottom) imply that it is possible; seems to m
On 12/05/2009, Jörg Schaible wrote:
> sebb wrote at Dienstag, 12. Mai 2009 11:22:
>
> [snip]
>
>
> > One other change needed to SVN:
> >
> > svn ps svn:eol-style native
> > src/main/java/org/apache/commons/compress/changes/ChangeSetResults.java
> > svn ps svn:eol-style native src/site/xdoc/d
>> I think similar, but this has been done automatically when following:
>> http://wiki.apache.org/commons/CreatingReleases
>
> Yes, I know; the original instructions (shown as outdated, at the
> bottom) imply that it is possible; seems to me it would be a lot
> better.
No its not outdated - just
sebb wrote at Dienstag, 12. Mai 2009 11:22:
[snip]
> One other change needed to SVN:
>
> svn ps svn:eol-style native
> src/main/java/org/apache/commons/compress/changes/ChangeSetResults.java
> svn ps svn:eol-style native src/site/xdoc/download_compress.xml
> svn ps svn:eol-style native
>
src/tes
On 12/05/2009, Christian Grobmeier wrote:
> >> Tag:
> >>
> https://svn.apache.org/repos/asf/commons/proper/compress/tags/commons-compress-1.0/
> >
> > I don't like the use of final tag names for release candidates; tags
> > should be immutable, so how can one generate another release candid
>> Tag:
>> https://svn.apache.org/repos/asf/commons/proper/compress/tags/commons-compress-1.0/
>
> I don't like the use of final tag names for release candidates; tags
> should be immutable, so how can one generate another release candidate
> if this one fails?
> I'm not sure what the solution to
>> jRPM has updated the license themself after i requested it.
>> See:
>> http://jrpm.svn.sourceforge.net/viewvc/jrpm/trunk/LICENSE.txt?revision=25&view=markup
>
> I see.
>
> That's actually the AL header, rather than the AL 2.0 License.
>
> The web-site still has:
>
> http://jrpm.sourceforge.net
On 11/05/2009, Christian Grobmeier wrote:
> >> jRPM appears to use AL 1.1 rather than AL 2.0, so the license text
> >> From the jrpm project should be added to LICENSE file.
> >
> > ISTR the code has been granted to the ASF and we have relicensed it -
> > I can't seem to find any paper trail,
>> jRPM appears to use AL 1.1 rather than AL 2.0, so the license text
>> From the jrpm project should be added to LICENSE file.
>
> ISTR the code has been granted to the ASF and we have relicensed it -
> I can't seem to find any paper trail, though.
jRPM has updated the license themself after i re
On 2009-05-11, sebb wrote:
> jRPM appears to use AL 1.1 rather than AL 2.0, so the license text
> From the jrpm project should be added to LICENSE file.
ISTR the code has been granted to the ASF and we have relicensed it -
I can't seem to find any paper trail, though.
> The OSGI information in
On 11/05/2009, Christian Grobmeier wrote:
> Hi all,
>
> as already discussed, I just created a RC1 for the first [compress] release
> :-)
> Let me know if you can find any problems.
>
> Cheers,
> Christian
>
>
> Tag:
>
> https://svn.apache.org/repos/asf/commons/proper/compress/tags/commons
testCpioUnarchive fails when building from the source tarball on
Windows because test1.xml has Unix linefeeds and thus is four bytes
shorter than expected - no reason to block the relase for me.
All my other tests passed.
There shouldn't be md5/sha1 checksums for the PGP signatures (they
probably
Hi all,
as already discussed, I just created a RC1 for the first [compress] release :-)
Let me know if you can find any problems.
Cheers,
Christian
Tag:
https://svn.apache.org/repos/asf/commons/proper/compress/tags/commons-compress-1.0/
Site:
http://people.apache.org/builds/commons/compress/1.
18 matches
Mail list logo