Re: My first commits...
On Tue, 6 Oct 2009 06:57:38 +0200, Christian Grobmeier wrote: > Christian, > why are you committing to a branch? We usually commit to the trunk > only. B/c of the commit messages we all can follow whats happening and > step in > Cheers > I would say that is how it is done elsewhere. Here, for most things, just commit to trunk. If it is a large refactor of something or a new feature then fair enough, maybe talk about it on the dev list and create a branch then if that is what is decided. > > On Tue, Oct 6, 2009 at 1:01 AM, Christian Hammers wrote: >> ...are not yet complete but trying to get everything into nice >> chunks takes some time. Feel free to make suggestions if I should put >> more or less into each commit. Looks ok to me, if you spot a typo that is a one line commit, do it, doesnt matter. If you are working on something that changes hundreds of lines of code, adds and deletes files etc, but that is the only way to do it without breaking trunk, then thats fine also. Dont worry about building up into chunks to make a nice commit, commit early and often is good, even for a few lines at a time. And, Welcome !!! :) >> >> bye, >> >> -christian- >> >> >> >> -- Gav... 16 degrees complete web solutions
RE: buildbot failure in ASF Buildbot on log4php-trunk
Apologies for the failed builds. Two things, I got buildbot email notifications working, so that's good at least. And I've solved most of the problems of https://issues.apache.org/jira/browse/INFRA-2294 Only thing left to do that I can see is the upgrade of phpunit. I can't remember how I got 3.4.x on there last time. apt-get, pecl and pear all have earlier versions causing the latest failure. So that now uninstalled and I'm looking at doing a manual install - unless someone replies Pretty quick with a better solution - 3.4.5 is latest release. Oh, and I changed buildbot to only report to the list on change of build - from pass to fail And from fail to pass, so repeated failures will now not be spamming us. Gav... > -Original Message- > From: [email protected] [mailto:[email protected]] > Sent: Wednesday, 30 December 2009 8:22 PM > To: [email protected] > Subject: buildbot failure in ASF Buildbot on log4php-trunk > > The Buildbot has detected a failed build of log4php-trunk on ASF > Buildbot. > Full details are available at: > http://ci.apache.org/builders/log4php-trunk/builds/294 > > Buildbot URL: http://ci.apache.org/ > > Buildslave for this Build: ceres_ubuntu > > Build Reason: forced: by IRC user on channel #asftest: > testing phpunit > Build Source Stamp: HEAD > Blamelist: > > BUILD FAILED: failed compile > > sincerely, > -The ASF Buildbot
RE: buildbot success in ASF Buildbot on log4php-trunk
Yay, phpunit 3.4.5 installed, and with the other reinstalls I did today, all tests now pass :) Buildbot is useful once more. Gav... > -Original Message- > From: [email protected] [mailto:[email protected]] > Sent: Wednesday, 30 December 2009 9:53 PM > To: [email protected] > Subject: buildbot success in ASF Buildbot on log4php-trunk > > The Buildbot has detected a restored build of log4php-trunk on ASF > Buildbot. > Full details are available at: > http://ci.apache.org/builders/log4php-trunk/builds/295 > > Buildbot URL: http://ci.apache.org/ > > Buildslave for this Build: ceres_ubuntu > > Build Reason: forced: by IRC user on channel #asftest: > testing phpunit 3.4.5 > Build Source Stamp: HEAD > Blamelist: > > Build succeeded! > > sincerely, > -The ASF Buildbot
RE: buildbot failure in ASF Buildbot on log4php-trunk
Sorry, fixed, an OS upgrade (today) meant that I needed to then link to sqlite3 instead of sqlite. Works again now. Gav... > -Original Message- > From: Christian Grobmeier [mailto:[email protected]] > Sent: Tuesday, 5 January 2010 4:24 PM > To: Log4PHP Dev > Subject: Re: buildbot failure in ASF Buildbot on log4php-trunk > > Outch I didn't nothing special, just added a new line a > changes.xml and corrected a constant name > > Modified: >incubator/log4php/trunk/src/changes/changes.xml > > incubator/log4php/trunk/src/main/php/helpers/LoggerOptionConverter.php > > Now its again PDO problem- isn't it weird?? > Last time it was related to phpunit update (which sounds odd) > > > > On Tue, Jan 5, 2010 at 7:59 AM, wrote: > > The Buildbot has detected a new failure of log4php-trunk on ASF > Buildbot. > > Full details are available at: > > http://ci.apache.org/builders/log4php-trunk/builds/296 > > > > Buildbot URL: http://ci.apache.org/ > > > > Buildslave for this Build: ceres_ubuntu > > > > Build Reason: > > Build Source Stamp: [branch incubator/log4php/trunk] 895917 > > Blamelist: grobmeier > > > > BUILD FAILED: failed compile > > > > sincerely, > > -The ASF Buildbot > > > >
RE: buildbot failure in ASF Buildbot on log4php-trunk
> -Original Message- > From: Christian Grobmeier [mailto:[email protected]] > Sent: Tuesday, 5 January 2010 5:10 PM > To: Log4PHP Dev > Subject: Re: buildbot failure in ASF Buildbot on log4php-trunk > > Gavin, > according to: > http://ci.apache.org/builders/log4php-trunk/builds/300 > my new testcase has been build. But its not visible online: > http://incubator.apache.org/log4php/coverage- > report/helpers_LoggerOptionConverter.php.html#277 > > wasn't it intended to push it to the site straight after a succesful > build? What happens is this: 1. commit to svn triggers buildbot. 2. buildbot runs tests, builds site ,docs etc 3. buildbot publishes 'immediately' to ci.apache.org/projects/log4php/* 4. a cron job on buildbot syncs changes to people.apache.org at 45 past every hour 5. a cron job on people.a.o syncs changes to main website servers every hour. So, there could be up to a 2 hour delay if timing is unlucky, but is usually an hour or less. Your page above can be seen currently at: http://ci.apache.org/projects/log4php/coverage-report/helpers_LoggerOptionConverter.php.html HTH Gav... > > Christian > > On Tue, Jan 5, 2010 at 7:37 AM, Gav... wrote: > > Sorry, fixed, an OS upgrade (today) meant that I needed to then link > to sqlite3 instead of sqlite. > > > > Works again now. > > > > Gav... > > > >> -Original Message- > >> From: Christian Grobmeier [mailto:[email protected]] > >> Sent: Tuesday, 5 January 2010 4:24 PM > >> To: Log4PHP Dev > >> Subject: Re: buildbot failure in ASF Buildbot on log4php-trunk > >> > >> Outch I didn't nothing special, just added a new line a > >> changes.xml and corrected a constant name > >> > >> Modified: > >>incubator/log4php/trunk/src/changes/changes.xml > >> > >> > incubator/log4php/trunk/src/main/php/helpers/LoggerOptionConverter.php > >> > >> Now its again PDO problem- isn't it weird?? > >> Last time it was related to phpunit update (which sounds odd) > >> > >> > >> > >> On Tue, Jan 5, 2010 at 7:59 AM, wrote: > >> > The Buildbot has detected a new failure of log4php-trunk on ASF > >> Buildbot. > >> > Full details are available at: > >> > http://ci.apache.org/builders/log4php-trunk/builds/296 > >> > > >> > Buildbot URL: http://ci.apache.org/ > >> > > >> > Buildslave for this Build: ceres_ubuntu > >> > > >> > Build Reason: > >> > Build Source Stamp: [branch incubator/log4php/trunk] 895917 > >> > Blamelist: grobmeier > >> > > >> > BUILD FAILED: failed compile > >> > > >> > sincerely, > >> > -The ASF Buildbot > >> > > >> > > > > > > >
RE: [VOTE] Graduate into Apache Logging
> -Original Message- > From: Christian Grobmeier [mailto:[email protected]] > Sent: Monday, 1 March 2010 4:59 PM > To: Log4PHP Dev > Subject: [VOTE] Graduate into Apache Logging > > Dear all, > > Log4PHP has successfully restarted last year. Meanwhile the project > has made its first release. It also has 3 active committers > contributing code on a regular basis. A good amount of e-mails have > been written on the mailinglists (avg: 101 on dev, 2 on users). > > Log4PHP has been in incubation since 2004. > > Please vote: > > [X] +1, graduate as Subproject into Apache Logging It's as ready as it can be I feel, the size of the project reflects the size of the work to do. The fact that it is going in as a sub-project makes this decision easier too. Gav... > [] -1, do not graduate because ... > > This vote is also running on the Logging General mailinglist. > > Best regards, > Christian
RE: Board report for March 2010
> -Original Message- > From: Christian Grobmeier [mailto:[email protected]] > Sent: Saturday, 6 March 2010 8:36 PM > To: Log4PHP Dev > Subject: Board report for March 2010 > > Hi all, > > I have quickly compiled a board report, since its due date is in a few > days. Here is my proposal. If you have changes on it, please come back > to this list > or change the text yourself on: > http://wiki.apache.org/incubator/March2010 > > It is also noted down on our wiki, but due to short time :-) I have > decided to add it to the incubator wiki immediatly - hope thats fine > to you all. Looking good, due to the successful vote by the IPMC on the incubator list, I tweaked it a little. Gav... > > Thanks, > Christian > > == March 2010 == > > Log4PHP is a logging framework similar to Log4J, but in PHP. The > project entered incubation in 2004, retired and restarted again on > 2007-07-04. After the first release, community feedback has increased. > The project is also in process of voting for graduation as a > subproject to Apache Logging. Since there are only positive reactions, > we expect a graduation very soon. > > * Bugfixes on 2.0.0 has been done > * Several new ideas of improvements have been collected in the issue > tracker > * Apache Log4PHP 2.0.0 (Incubating) has been released on 12.12.2009
RE: Steps after Graduation
> -Original Message- > From: Christian Grobmeier [mailto:[email protected]] > Sent: Thursday, 11 March 2010 9:38 PM > To: [email protected]; Log4PHP Dev > Subject: Steps after Graduation > > Hi all, > > sorry for crossposting to log4php-dev and general - I was unsure if > all people are subscribed to all lists. > However, I would like to catch all the necessary actions for post > graduation in this e-mail thread. > > So far i found: > http://incubator.apache.org/guides/graduation.html#life-after- > graduation > > As Log4PHP graduated as a subproject, it seems that only a handover > between chairs is necessary. How is this done? Is this public? Should be, I have already asked the IPMC Chair (Noel) to initiate the handover - it was in my result vote message to gene...@incubator - I'll give him another couple of days before prodding again - in the meantime we can't do any more steps. > > > These are other necessary actions: > * Move Log4PHP website from http://incubator.apache.org/log4php/ to > logging.apache.org/log4php > * Modify Logging.apache.org website and tell people that log4php is > not longer incubating > * Write blog post and let people know > * Modify Log4PHP webpage, remove incubator logo, update info > * Move SVN from: http://svn.apache.org/repos/asf/incubator/log4php/ to > http://svn.apache.org/repos/asf/logging/log4php Sounds good, if you file the svn move as an infra issue, I can do that. We need to update the Log4PHP incubator status page too, and move us from Incubating to graduated also. > > Is it necessary to move the incubator release to a new location (it > was version 2.0.0)? Since a new 2.1.0 could be created soon, this > might be left out. Not sure, I think that the release area gets removed, but the release will remain in the dist archives area, I'll check before we do anything. > Is there a problem with SVN rights we need to take care of? Probably, I can take care of it as it crops up. The Logging PMC Chair should add the Log4PHP committers to the svn auth file. First step is to wait for Noel to ack the move. Gav... > > I would be glad if somebody could help out or give me pointers how to > solve all of this. If you have more things to do, please answer to > this thread also > > Thanks > Christian
RE: Steps after Graduation
> -Original Message- > From: Christian Grobmeier [mailto:[email protected]] > Sent: Friday, 19 March 2010 1:54 AM > To: Log4PHP Dev > Subject: Re: Steps after Graduation > > Hi, > > >> As Log4PHP graduated as a subproject, it seems that only a handover > >> between chairs is necessary. How is this done? Is this public? > > > > Should be, I have already asked the IPMC Chair (Noel) to initiate the > > handover - it was in my result vote message to gene...@incubator - > > I'll give him another couple of days before prodding again - in the > > meantime we can't do any more steps. > > are there any news? Yep, we have the green light to go. Gav... > > best regards, > Christian
RE: Steps after Graduation
> -Original Message- > From: Christian Grobmeier [mailto:[email protected]] > Sent: Monday, 22 March 2010 3:47 PM > To: Log4PHP Dev > Subject: Re: Steps after Graduation > > >> are there any news? > > > > Yep, we have the green light to go. > > Perfect. I filed SVN move as infra issues: > https://issues.apache.org/jira/browse/INFRA-2562 This is now done. Anyone with trunk/site/branches checked out should do: svn switch https://svn.apache.org/repos/asf/logging/log4php from their local copy. substitute https for http if you don’t have that version checked out. Gav...
RE: Steps after Graduation
> -Original Message- > From: Christian Grobmeier [mailto:[email protected]] > Sent: Monday, 22 March 2010 9:03 PM > To: Log4PHP Dev > Subject: Re: Steps after Graduation > > Great thanks! > I will deal with the site content pointing to the new svn tomorrow. > > Site location needs to be changed too - will you deal with that or > should I? > If it is me, can you tell me where i should look for the script? I can do that bit. Someone will need to update the logging.apache.org site to point to /log4php also. Gav... > > > On Mon, Mar 22, 2010 at 12:00 PM, Gav... > wrote: > > > > > >> -Original Message- > >> From: Christian Grobmeier [mailto:[email protected]] > >> Sent: Monday, 22 March 2010 3:47 PM > >> To: Log4PHP Dev > >> Subject: Re: Steps after Graduation > >> > >> >> are there any news? > >> > > >> > Yep, we have the green light to go. > >> > >> Perfect. I filed SVN move as infra issues: > >> https://issues.apache.org/jira/browse/INFRA-2562 > > > > This is now done. > > > > Anyone with trunk/site/branches checked out should do: > > > > svn switch https://svn.apache.org/repos/asf/logging/log4php > > > > from their local copy. substitute https for http if you don’t have > that version checked out. > > > > Gav... > > > > > > > >
RE: Steps after Graduation
> -Original Message- > From: Christian Grobmeier [mailto:[email protected]] > Sent: Monday, 22 March 2010 10:45 PM > To: Log4PHP Dev > Subject: Re: Steps after Graduation > > > Someone will need to update the logging.apache.org site to point to > /log4php also. > > I am not sure if I have the rights but I will try that also As a logging PMC member, you do :) > > > > > > Gav... > > > >> > >> > >> On Mon, Mar 22, 2010 at 12:00 PM, Gav... > >> wrote: > >> > > >> > > >> >> -Original Message- > >> >> From: Christian Grobmeier [mailto:[email protected]] > >> >> Sent: Monday, 22 March 2010 3:47 PM > >> >> To: Log4PHP Dev > >> >> Subject: Re: Steps after Graduation > >> >> > >> >> >> are there any news? > >> >> > > >> >> > Yep, we have the green light to go. > >> >> > >> >> Perfect. I filed SVN move as infra issues: > >> >> https://issues.apache.org/jira/browse/INFRA-2562 > >> > > >> > This is now done. > >> > > >> > Anyone with trunk/site/branches checked out should do: > >> > > >> > svn switch https://svn.apache.org/repos/asf/logging/log4php > >> > > >> > from their local copy. substitute https for http if you don’t have > >> that version checked out. > >> > > >> > Gav... > >> > > >> > > >> > > >> > > > > > > >
RE: [jira] Created: (LOG4PHP-107) Site should updated via svn
erm, generated docs in svn, yuck. what is wrong with buildbot doing the mvn site deploy straight to the website location? Gav... > -Original Message- > From: Christian Grobmeier (JIRA) [mailto:[email protected]] > Sent: Friday, 26 March 2010 3:51 PM > To: [email protected] > Subject: [jira] Created: (LOG4PHP-107) Site should updated via svn > > Site should updated via svn > --- > > Key: LOG4PHP-107 > URL: https://issues.apache.org/jira/browse/LOG4PHP-107 > Project: Log4php > Issue Type: Task > Components: Website > Reporter: Christian Grobmeier > > > Currently logging uses mvn site site-deploy to commit the generated > page into svn. On the webserver they do svn update. We have been asked > to follow this process too > > -- > This message is automatically generated by JIRA. > - > You can reply to this email to add a comment to the issue online.
RE: How is log4php capitalized?
> -Original Message- > From: Ivan Habunek [mailto:[email protected]] > Sent: Tuesday, 27 July 2010 7:34 AM > To: Log4PHP Dev > Subject: Re: How is log4php capitalized? > > On 26.7.2010. 23:28, Christian Grobmeier wrote: > > Are you volunteering to fix this mispelled ones? :-) > > OK, I'm the new kid, I'll do it. :) > > So can I go ahead with "Apache log4php" or does anybody have any > objections or proposals? nope, looks fine to me. +1 Gav... > > Ivan
