Can I get access to NEXUS to test my changes?
On 04/04/2012 09:08 PM, Brock Noland wrote:
I think this is probably OK, it seems like these rules are not hard and fast.
On Wed, Apr 4, 2012 at 9:05 PM, Jim Donofrio<[email protected]> wrote:
Ok I will make the file NOTICE.txt contain the NOTICE.txt for the source
distribution. I will leave the notice for the convenience binary at the root
of the svn but call it BIN-NOTICE.txt to be clear that it is for the binary
distribution. Is this ok?
I took this example from Whirr, so maybe someone should let them know to
also fix their distributions.
On 04/04/2012 07:30 PM, sebb wrote:
On 4 April 2012 15:33, Marvin Humphrey<[email protected]> wrote:
On Wed, Apr 4, 2012 at 4:13 AM, Brock Noland<[email protected]> wrote:
On Wed, Apr 4, 2012 at 4:33 AM, sebb<[email protected]> wrote:
The tag to be voted upon:
http://svn.apache.org/repos/asf/incubator/mrunit/tags/release-0.9.0-incubating/
There's a NOTICE.txt and NOTICE-src.txt at the top level.
IMO the primary NOTICE file should be for the source.
So there would be a NOTICE-bin.txt and a NOTICE.txt?
The Apache License 2.0 only makes mention of a "NOTICE" file, not
"NOTICE-bin"
(or "NOTICE-src").
The top priority is that the NOTICE[.txt] file in the canonical source
release
be correct and complete. That's what we're voting on and what the ASF is
endorsing.
+1
I haven't yet arrived at a position regarding the -bin/-deps situation.
At
this point, I wouldn't -1 a source release that contains irrelevant and
misleading information in a file called "NOTICE-bin.txt" about
dependencies
which are not present, but that could change.
So long as the file is called NOTICE.txt (or NOTICE) and is at the
top-level of a binary archive, it does not matter what it is called in
SVN. To avoid confusion, probably best to rename or move the version
of the NOTICE file for binary releases. Since the binary file is just
an extended version of the source NOTICE file (at least in this case),
the binary version could be generated by concatenation.
Marvin Humphrey
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
