You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4cxx-dev@logging.apache.org by Christian Grobmeier <gr...@gmail.com> on 2014/01/02 11:10:56 UTC
Re: January 2014 podling report content
On 30 Dec 2013, at 19:41, Joseph Southwell wrote:
> Sorry, Wrong thread. I was not offering to take lead. Experienced
> programmer, beginner at open source.
There are no "leaders" at Apache. There are just people who "do the
things", and if you do it, you "lead" (in a way).
And you are very welcome here, even when you just start with open
source.
Cheers
>
> Joseph Southwell
> joseph@southwell.org
> The past is history,
> The future's a mystery,
> The present's a gift.
>
>
> On Dec 30, 2013, at 12:34 PM, Joseph Southwell <jo...@southwell.org>
> wrote:
>
>> I am probably willing too. I just currently don't know what I would
>> be promising.
>>
>> Joseph Southwell
>> joseph@southwell.org
>> The past is history,
>> The future's a mystery,
>> The present's a gift.
>>
>>
>> On Dec 30, 2013, at 11:10 AM, Thorsten Schöning
>> <ts...@am-soft.de> wrote:
>>
>>> Guten Tag Rhys Ulerich,
>>> am Montag, 30. Dezember 2013 um 16:04 schrieben Sie:
>>>
>>>> Agreed. Have a preference for the branch name for the development
>>>> line? No logging convention jumps out at my from looking at, e.g.,
>>>> https://svn.apache.org/repos/asf/logging/log4j/log4j2/branches/.
>>>
>>> I would go with log4j and use version specific names, like 0.11.2,
>>> 0.12.0, 1.0.0 etc.
>>>
>>>> Once https://issues.apache.org/jira/browse/INFRA-7092 closes,
>>>> should
>>>> we start with getting that 0.11.0 release branch made from src on
>>>> carnold's last commit?
>>>
>>> Yes.
>>>
>>>> If so, anyone want to take lead there when the
>>>> time comes?
>>>
>>> I would give it a try, but I would focus on formalism alone and
>>> wouldn't test anything myself. I currently simply don't have the
>>> environment to do so and in my opinion any real development should
>>> go
>>> into 0.12.0. Your linked examples of the release process contain
>>> statements about tests, so would it be ok to just ignore those
>>> things?
>>> From my point of view releasing the current status of the code with
>>> all the patches applied would be a reasonable goal.
>>>
>>> Mit freundlichen Grüßen,
>>>
>>> Thorsten Schöning
>>>
>>> --
>>> Thorsten Schöning E-Mail:Thorsten.Schoening@AM-SoFT.de
>>> AM-SoFT IT-Systeme http://www.AM-SoFT.de/
>>>
>>> Telefon...........05151- 9468- 55
>>> Fax...............05151- 9468- 88
>>> Mobil..............0178-8 9468- 04
>>>
>>> AM-SoFT GmbH IT-Systeme, Brandenburger Str. 7c, 31789 Hameln
>>> AG Hannover HRB 207 694 - Geschäftsführer: Andreas Muchow
>>>
>>
---
http://www.grobmeier.de
The Zen Programmer: http://bit.ly/12lC6DL
@grobmeier
GPG: 0xA5CC90DB