Hello Stefan, I just thought that a separate branch from the current would help us develop some features (mosty a zeroMq appender I am currently using and a ado.net hierarchy manager) and correct some bugs and having a "clean" way of merging them back to the trunk.
If there is a schedule for 1.2.11 I don't mind a branch after that. If there is not a schedule for 1.2.11 or there are resource constraints I could certainly help time to drive a good release. As have been noted in other messages, there is an issue with the strong naming of log4net assembly. That prevents lots of people from creating their own assembly as there are dependencies that have to be recompiled. In my situation e.g. I have windsor IOC (among other things) that would take a great effort to build. So if what is needed to have stuff merged is resources, I am willing to do what is required. Regards Tasos Vogiatzoglou On Wed, Aug 17, 2011 at 1:22 PM, Stefan Bodewig <bode...@apache.org> wrote: > Hi Tasos, > > On 2011-08-10, Tasos Vogiatzoglou wrote: > >> Could anyone with write access make a .NET 4 (or 1.2.11 ?) branch in >> the repos ? I have submitted some patches that would be helpfull to >> have them included and I am working on the same line on the test >> project. > > What exactly would you need? I could certainly copy current svn trunk > to a branch but don't expect to merge any of the patches that need to go > into the 1.2.11 release over there. Does that help you? > > Would it make sense to wait until 1.2.11 is released? > > If you are familiar with hg or git it may be easier to work from > http://git.apache.org/log4net.git/ or the hg mirror Dominik has setup so > nobody had to manually maintain the svn branch. > > Stefan >
