commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From sebb <seb...@gmail.com>
Subject Re: [VOTE] Release commons-fileupload 1.2.1 (rc3)
Date Thu, 10 Jan 2008 17:23:19 GMT
On 10/01/2008, Niall Pemberton <niall.pemberton@gmail.com> wrote:
> On Jan 10, 2008 3:41 PM, sebb <sebbaz@gmail.com> wrote:
> > On 10/01/2008, Jochen Wiedmann <jochen.wiedmann@gmail.com> wrote:
> > > I forgot to note: The distribution is available on
> > >
> > >    http://people.apache.org/~jochen/commons-fileupload/dist
> >
> > -1:
> > The NOTICE files in the jars are non-standard. They also refer to
> > Commons-IO which is not part of the jar. The NOTICE file is *only* for
> > items that are included in the distribution, not external
> > dependencies.
>
> Is this true? I realize the following document has still (after 18
> months) not yet been made official ASF policy, but in the absence of
> any other then there are two sections which seem relevant:
>  - System Requirements
>  - Optional Add-ons
> http://people.apache.org/~rubys/3party.html#options-systemrequirements
>
> If for example we have component which can use 3rd Party work that
> comes under the "excluded licenses" (from memory I think VFS did this)
> then we have an obligation to inform the users of this and the NOTICE
> file seems an appropriate place to do this. Having the dependencies
> and their licenses listed seems like a *good thing* to me for users to
> be confident of all the licensing implications of using a distro.
> Anyway if theres contention on the format of the NOTICE in this
> release then we should ask on legal-discuss to see if we can get an
> answer whether its valid or not. I will try to do this later but I'm
> going out soon - so hopefully someone else will beat me to it.
>

I think the above is mainly about including the 3rd party code in
distributions ... "inclusion within"

See:
http://www.apache.org/legal/src-headers.html#NOTICE
for details of the NOTICE contents.

> Niall
>
> > The NOTICE.txt files in the archives are OK; the same files should be
> > in the jars.
> >
> > -0: MD5 and SHA1 files should have "space *" - not just a single space
> > - between the hash and the filename. This should be fixed if there are
> > any other reasons to recreate them.
> >
> > > The proposed site is at
> > >
> > >    http://people.apache.org/~jochen/commons-fileupload/site
> >
> > Cannot find any reference to which versions of Java are supported.
> >
> > What does "(optional)" mean in the Dependencies section under Commons IO?
> >
> > Javadoc footer looks wrong:
> >
> > Copyright Â(c)
> >
> > Not sure what the A-circumflex character is doing there.
> > Should probably use &copy; instead of actual characters if possible
> > (as is done in the cross-reference)
> >
> > I assume that the SVN tag is:
> >
> > http://svn.apache.org/viewvc/commons/proper/fileupload/tags/commons-fileupload-1.2.1rc3/
> >
> >
> > > Sorry,
> > >
> > > Jochen
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> > > For additional commands, e-mail: dev-help@commons.apache.org
> > >
> > >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> > For additional commands, e-mail: dev-help@commons.apache.org
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org


Mime
View raw message