Johannes Frandsen wrote:
could we focus on committing code that doesn't break log4php....
We have been doing that for quite some time now. But there has also been
a wish to clean up naming and structure. This is the time to fix it
(before we release 2.0). By bumping the version number from 0.9 to 2.0
we should be allowed to do these changes.
I recognize that log4php never actually has been labeled as stable but
I have used it as svn external in my project for several months
without problems until today where everything starts to break.
That you use svn:externals on another project trunk is your own risk.
If major rewrites are in the making could we create a stable branch
meanwhile!
Why not just check out the revision you would like to use? The last
"stable" release of log4php was 0.9 many years ago. We haven't
officially release the PHP 5 version yet. And we are working on many
minor and major improvements which we hope everyone using log4php will
appreciate when we release a stable version.
So in recap....... love the increased activity on this project....love
the project......but please check your code before you commit major
changes or update the website before you make the changes
Some of the changes today will break because I have to change a few
things over more than 1-2 commits. Sorry, but that's how trunk works. It
will be a bit unstable from time to time, but the cleanup is always
around the corner :)
Knut
