You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@river.apache.org by Peter Firmstone <ji...@zeus.net.au> on 2010/01/30 08:24:48 UTC
Apache River Release - Voting Period
I've just updated the Apache River 2.1.2 Release artifacts, available on
http://people.apache.org/~peter_firmstone/
I'll run apache RAT shortly, so these might be updated tomorrow, if I
find any problems, however feel free to do your own auditing.
I propose a Voting Period of 5 days, (minimum allowed is 72 hours)
commencing Monday the 1st of February, ending on Friday the 5th of February.
Best Regards,
Peter Firmstone.
Re: Apache River Release - Voting Period
Posted by Peter Firmstone <ji...@zeus.net.au>.
Thanks Jukka,
If all the source *.java and *.html files contain the library headers
will this be sufficient?
Don't really want to edit all the *.td or policy files.
Cheers,
Peter.
Which Files Must Contain An ASF License Text?
Every source file must contain the appropriate ASF License text.
Is A Full Copy Of The License Required In Each Source File?
In short, only one copy of the license is needed per distribution. This
full license file should be placed at the root of the distribution in a
file named LICENSE. For software developed at the ASF, each source file
need only contain the boilerplate notice
<http://www.apache.org/legal/src-headers.html#headers>.
Jukka Zitting wrote:
> Hi,
>
> On Sun, Jan 31, 2010 at 10:58 AM, Peter Firmstone <ji...@zeus.net.au> wrote:
>
>> Does the following mean I shouldn't include the qa or test directory's
>> http://www.apache.org/dev/release.html#what
>>
>> How Do The Types Of Apache Software Distribution Differ?
>>
>> * *Test Packages* are not Apache releases. All releases require due
>> process and official approval. Test packages are for testing
>> ongoing development and should only be discussed on the project
>> development lists.
>>
>
> This refers to things like nightly snapshots that are made available
> for people to test the latest code in the trunk.
>
> BR,
>
> Jukka Zitting
>
>
Re: Apache River Release - Voting Period
Posted by Jukka Zitting <ju...@gmail.com>.
Hi,
On Sun, Jan 31, 2010 at 10:58 AM, Peter Firmstone <ji...@zeus.net.au> wrote:
> Does the following mean I shouldn't include the qa or test directory's
> http://www.apache.org/dev/release.html#what
>
> How Do The Types Of Apache Software Distribution Differ?
>
> * *Test Packages* are not Apache releases. All releases require due
> process and official approval. Test packages are for testing
> ongoing development and should only be discussed on the project
> development lists.
This refers to things like nightly snapshots that are made available
for people to test the latest code in the trunk.
BR,
Jukka Zitting
Re: Apache River Release - Voting Period
Posted by Peter Firmstone <ji...@zeus.net.au>.
I noticed there are some issues with qa in the RAT report.
Does the following mean I shouldn't include the qa or test directory's
http://www.apache.org/dev/release.html#what
How Do The Types Of Apache Software Distribution Differ?
* *Test Packages* are not Apache releases. All releases require due
process and official approval. Test packages are for testing
ongoing development and should only be discussed on the project
development lists.
I've also just updated the release artifacts at:
people.apache.org/~peter_firmstone/
Including the RAT reports.
Regards,
Peter.
Craig L Russell wrote:
> Hi Niclas,
>
> On Jan 30, 2010, at 5:39 PM, Niclas Hedhman wrote:
>
>>> I'll run apache RAT shortly, so these might be updated tomorrow, if
>>> I find
>>> any problems, however feel free to do your own auditing.
>>
>> RAT is normally run before announcing the availability and placed
>> alongside the artifacts to be released.
>>
> Beg pardon, but RAT is normally run before the vote is conducted so
> the voters can see the RAT output before they review the release.
>
> Craig
>
> Craig L Russell
> Assistant Secretary, Apache Software Foundation
> Chair, OpenJPA PMC
> clr@apache.org http://db.apache.org/jdo
>
>
>
>
>
>
>
>
>
Re: Apache River Release - Voting Period
Posted by Craig L Russell <Cr...@Sun.COM>.
Hi Niclas,
On Jan 30, 2010, at 5:39 PM, Niclas Hedhman wrote:
>> I'll run apache RAT shortly, so these might be updated tomorrow, if
>> I find
>> any problems, however feel free to do your own auditing.
>
> RAT is normally run before announcing the availability and placed
> alongside the artifacts to be released.
>
Beg pardon, but RAT is normally run before the vote is conducted so
the voters can see the RAT output before they review the release.
Craig
Craig L Russell
Assistant Secretary, Apache Software Foundation
Chair, OpenJPA PMC
clr@apache.org http://db.apache.org/jdo
Re: Apache River Release - Voting Period
Posted by Peter Firmstone <ji...@zeus.net.au>.
Ok, I've run RAT, there were some source files without headers, this has
now been fixed and committed.
The updated RAT reports are attached.
I'll update the release artifacts after my build completes.
Regards,
Peter Firmstone.
Niclas Hedhman wrote:
> On Sat, Jan 30, 2010 at 3:24 PM, Peter Firmstone <ji...@zeus.net.au> wrote:
>
>> I've just updated the Apache River 2.1.2 Release artifacts, available on
>> http://people.apache.org/~peter_firmstone/
>>
>
> Excellent. I won't have the cycles to check this myself, as I am
> moving to a new country at the moment, and need to settle in.
>
>
>> I'll run apache RAT shortly, so these might be updated tomorrow, if I find
>> any problems, however feel free to do your own auditing.
>>
>
> RAT is normally run before announcing the availability and placed
> alongside the artifacts to be released.
>
>
>> I propose a Voting Period of 5 days, (minimum allowed is 72 hours)
>> commencing Monday the 1st of February, ending on Friday the 5th of February.
>>
>
> AFAIK, it is not required to have a 'boxed timeframe' determined
> upfront. The 72 hours minimum is essentially there to ensure that
> everyone has a chance to chime in on every topic, even if they are
> travelling, week end with family and so on. The upper limit is
> basically by function of the availability of the one that drives the
> vote. If he/she is ready on 73rd hour and has good reason to believe
> that there is consensus in the community, the vote can be concluded.
> If such person is unavailable for an additional 5 days, the vote may
> run longer.
>
>
> Cheers
>
Re: Apache River Release - Voting Period
Posted by Niclas Hedhman <ni...@hedhman.org>.
On Sat, Jan 30, 2010 at 3:24 PM, Peter Firmstone <ji...@zeus.net.au> wrote:
> I've just updated the Apache River 2.1.2 Release artifacts, available on
> http://people.apache.org/~peter_firmstone/
Excellent. I won't have the cycles to check this myself, as I am
moving to a new country at the moment, and need to settle in.
> I'll run apache RAT shortly, so these might be updated tomorrow, if I find
> any problems, however feel free to do your own auditing.
RAT is normally run before announcing the availability and placed
alongside the artifacts to be released.
> I propose a Voting Period of 5 days, (minimum allowed is 72 hours)
> commencing Monday the 1st of February, ending on Friday the 5th of February.
AFAIK, it is not required to have a 'boxed timeframe' determined
upfront. The 72 hours minimum is essentially there to ensure that
everyone has a chance to chime in on every topic, even if they are
travelling, week end with family and so on. The upper limit is
basically by function of the availability of the one that drives the
vote. If he/she is ready on 73rd hour and has good reason to believe
that there is consensus in the community, the vote can be concluded.
If such person is unavailable for an additional 5 days, the vote may
run longer.
Cheers
--
Niclas Hedhman, Software Developer
http://www.qi4j.org - New Energy for Java
I live here; http://tinyurl.com/2qq9er
I work here; http://tinyurl.com/2ymelc
I relax here; http://tinyurl.com/2cgsug