Hi Ivan,
Can you look at LOG4PHP-213 and LOG4PHP-204 for 2.3.1. It has been sitting
there for a long time.
PS: nice to have you back.
Thanks
On Sun, Dec 1, 2013 at 12:41 PM, Ivan Habunek wrote:
> I'd like to start the release procedure for 2.3.1 next week. Does
> anybody have something which
Thanks, that's almost exactly the answer I was hoping for. :)
> Ivan Habunek hat am 1. Dezember 2013 um 13:16
> geschrieben:
>
>
> Well, tagging on git is simple. We already have the current and
> previous releases tagged, and you can install them via composer:
> https://packagist.org/packages/ap
Well, tagging on git is simple. We already have the current and
previous releases tagged, and you can install them via composer:
https://packagist.org/packages/apache/log4php
But there's a lot more to be done to release a new version of an
Apache project. Here's the current (slightly outdated) rel
Hi, Ivan!
Great you are doing this, so thank you in advance!
The question from my side is: How complicated is it to actually release a
version?
I've been working with GIT repositories for quite some time, and I also really
like the way Composer influences the way new versions are made available
I'd like to start the release procedure for 2.3.1 next week. Does
anybody have something which they really want in 2.3.1? Please hold of
any non-critical changes if possible. We need this release to
establish a new release procedure, with a new web site and moving docs
to Sphinx (see "docs" branch
