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) release procedure to give you an idea: http://wiki.apache.org/logging-log4php/ReleaseProcedure I will update it as I create the next release. Have to replace SVN with Git and some other changes. Until now, since docs were integrated in the web site, we had to generate a new web site for each release. We're doing away with that from next release. The web site will be generated by Apache CMS, and the docs will be separate, generated by Sphinx. So that will make things somewhat easier. And from version 3.0.0 I want to replace Maven with Phing which is much more lightweight, and makes more sense for a PHP project which already uses Composer internally. Regards, Ivan On 1 December 2013 12:57, [email protected] <[email protected]> wrote: > 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 to the public: If you tag a version in GIT, it is available almost > instantly (provided there is a post-commit-hook installed that triggers > detection of "packagist.org"). > > Regards, > Sven > >> Ivan Habunek <[email protected]> hat am 1. Dezember 2013 um 12:41 >> geschrieben: >> >> >> 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 in Git). >> >> Regards, >> Ivan
