Mailing-List: contact bloodhound-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: bloodhound-dev@incubator.apache.org
Received-SPF: pass (athena.apache.org: domain of gary.martin@wandisco.com
 designates 209.85.215.46 as permitted sender)
Message-ID: <50ED7473.2060600@wandisco.com>
Date: Wed, 09 Jan 2013 13:45:23 +0000
From: Gary Martin <gary.martin@wandisco.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
 rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: bloodhound-dev@incubator.apache.org
Subject: Re: [Apache Bloodhound] #273: Verify trac/contrib is granted to trac
 or remove for next release
References: <052.49f34959ac10810d14835a38d0e236e8@incubator.apache.org>
 <067.fff8ff22fa4cb6ce80d2b022ac870b42@incubator.apache.org>
In-Reply-To: <067.fff8ff22fa4cb6ce80d2b022ac870b42@incubator.apache.org>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit

On 05/01/13 12:59, Apache Bloodhound wrote:
> #273: Verify trac/contrib is granted to trac or remove for next release
> ------------------------+-----------------------
>    Reporter:  gjm        |      Owner:  nobody
>        Type:  task       |     Status:  new
>    Priority:  blocker    |  Milestone:  Release 4
>   Component:  dashboard  |    Version:
> Resolution:             |   Keywords:
> ------------------------+-----------------------
>
> Comment (by rjollos):
>
>   [trac:#11006] is the ticket that these changes will be made against.
>
That is excellent. I take it that this investigation will assert from 
each relevant author that the source files can be provided with headers 
of a form consistent with Trac practice.

Although I would like to assume that this would effectively be enough to 
resolve the issue, I imagine that this will take some time to complete 
so it may be best to remove the directory for the upcoming release 
during the preparation of the release tarball. If we include a note to 
this effect in our documentation we can point out that these files will 
still be available if required through svn and we can let this issue 
spill over to the next release.

Cheers,
     Gary