Re: [VOTE] Release RC3 as Log4PHP 2.0.0

[Curt Arnold <ca...@apache.org>]

I was able to nearly rebuild the release which had only minor variations from in the generated documentation.  Every generated docfile had a "Documentation generated by" timestamp which obviously varied.  The other issue is that my check build had a few places where classes appeared in different order (Direct Dependents in docs/log4php/LoggerAppender.html, for example).  The release build was alphabetically sorted while mine had no obvious sort order.

Took a little trial and error to get a configuration down, but from a non stock Ubuntu 9.04 with Sun Java 6, Apache Maven 2 and PHP 5 already installed, I still needed to do:

sudo pear upgrade PEAR
sudo pear channel-discover pear.phpunit.de
sudo pear install phpunit/PHPUnit
sudo apt-get install php5-xdebug
sudo pear install XML_Serializer-0.19.2
sudo pear install --alldeps PEAR_PackageFileManager2


Then ran:

mvn site assembly:assembly

mvn rat:check reports that many of the generated documentation files do not have ASF source file headers as previously noted.

Reproducible, no obvious legal issues other than the generated doc issue.  Here is my +1 to push it to the Incubator PMC.

Re: [VOTE] Release RC3 as Log4PHP 2.0.0

[Curt Arnold <ca...@apache.org>]

On Dec 3, 2009, at 4:45 PM, Christian Grobmeier wrote:

> Thanks Curt! I appreciate your effort and will document your installation guide
> How many +1 are necessary for pushing forward?
> 

Three binding +1's and 72 hours elapsed is the general practice.  I checked the asf-authorization file and all three +1's are in the logging-log4php group which is my best approximation of the PPMC membership list, so I think we have three binding votes and we've exceeded 72 hours.  I think we are good to go to the Incubator PMC.

http://incubator.apache.org/guides/releasemanagement.html#release-guidelines
> 
> Incubator Release Vote
> 
> All releases by podlings must be approved by the TODO: link Incubator PMC. The conventional process is for the podling to follow the usual Apache process (including TODO: link release vote) and then call for a Incubator PMC VOTE on the TODO: link general incubator list.
> 
> The release manager should post the call for the VOTE.
> 
> 	• Links to the release artifacts
> 	• Links to the PPMC release vote thread
> 	• Link to the tag from which the release is cut
> 
> Release managers should subscribe to a number of Apache-wide mailing lists. Decisions are taken on these mailing lists and issues resolved. Documentation is updated later (if at all). It's important that release managers ensure that they keep up to date.
> 
> 	• TODO: link General infrastructure list
> 	• TODO: link Legal discuss list
> Release managers for incubating podlings should also subscribe to the TODO: link general list. 

Re: [VOTE] Release RC3 as Log4PHP 2.0.0

[Christian Grobmeier <gr...@gmail.com>]

Thanks Curt! I appreciate your effort and will document your installation guide
How many +1 are necessary for pushing forward?


On Thu, Dec 3, 2009 at 4:12 AM, Curt Arnold <ca...@apache.org> wrote:
> I was able to nearly rebuild the release which had only minor variations from in the generated documentation.  Every generated docfile had a "Documentation generated by" timestamp which obviously varied.  The other issue is that my check build had a few places where classes appeared in different order (Direct Dependents in docs/log4php/LoggerAppender.html, for example).  The release build was alphabetically sorted while mine had no obvious sort order.
>
> Took a little trial and error to get a configuration down, but from a non stock Ubuntu 9.04 with Sun Java 6, Apache Maven 2 and PHP 5 already installed, I still needed to do:
>
> sudo pear upgrade PEAR
> sudo pear channel-discover pear.phpunit.de
> sudo pear install phpunit/PHPUnit
> sudo apt-get install php5-xdebug
> sudo pear install XML_Serializer-0.19.2
> sudo pear install --alldeps PEAR_PackageFileManager2
>
>
> Then ran:
>
> mvn site assembly:assembly
>
> mvn rat:check reports that many of the generated documentation files do not have ASF source file headers as previously noted.
>
> Reproducible, no obvious legal issues other than the generated doc issue.  Here is my +1 to push it to the Incubator PMC.
>
>
>