On Fri, Jan 31, 2014 at 02:04:02PM -0800, Rui Paulo wrote:
> On 20 Jan 2014, at 13:49, Glen Barber <g...@freebsd.org> wrote:
> 
> > Author: gjb
> > Date: Mon Jan 20 21:49:59 2014
> > New Revision: 260927
> > URL: http://svnweb.freebsd.org/changeset/base/260927
> > 
> > Log:
> >  Trim copyright years.
> >  Add missing punctuation.
> >  Use <quote></quote> in place of literal quotes.
> > 
> >  Sponsored by:      The FreeBSD Foundation
> > 
> > Modified:
> >  head/release/doc/en_US.ISO8859-1/relnotes/article.xml
> > 
> > Modified: head/release/doc/en_US.ISO8859-1/relnotes/article.xml
> > ==============================================================================
> > --- head/release/doc/en_US.ISO8859-1/relnotes/article.xml   Mon Jan 20 
> > 20:56:09 2014        (r260926)
> > +++ head/release/doc/en_US.ISO8859-1/relnotes/article.xml   Mon Jan 20 
> > 21:49:59 2014        (r260927)
> > @@ -12,20 +12,6 @@
> >   <pubdate>$FreeBSD$</pubdate>
> > 
> >   <copyright>
> > -    <year>2000</year>
> > -    <year>2001</year>
> > -    <year>2002</year>
> > -    <year>2003</year>
> > -    <year>2004</year>
> > -    <year>2005</year>
> > -    <year>2006</year>
> > -    <year>2007</year>
> > -    <year>2008</year>
> > -    <year>2009</year>
> > -    <year>2010</year>
> > -    <year>2011</year>
> > -    <year>2012</year>
> > -    <year>2013</year>
> >     <year>2014</year>
> 
> Is this a good idea?  I've heard arguments that keeping all these
> years is the right approach, but at least we should have 2000-2014,
> no?
> 

There are a number of problems with these documents at this point.  To
be honest, the copyright years in the document really are the least of
my concerns with them right now.

But, are the release notes for a specific version of FreeBSD copyrighted
for the entirety of the Project as a whole, or the year(s) the release
in question was in the release cycle?  I do not know the answer.

Similar was done for 9.2-RELEASE, and I think 8.4-RELEASE, fwiw.

Glen

Attachment: pgpLNDoYctKDp.pgp
Description: PGP signature

Reply via email to