Re: [Koha-devel] Post-3.0 git branch and version numbering

[Henri-Damien LAURENT]

Galen Charlton a écrit :
> Hi,
>
> On Mon, Aug 11, 2008 at 10:25 AM, Chris Cormack
> <address@hidden> wrote:
>   
> > I guess the next question is who is doing the release Maintainers role, for 3.0?
> > The last time there was discussion on this on irc (on the 7/7/2008).
> > Biblibre offered to fill the role.
> > Does that offer still stand? If so, here's one vote for them to take
> > up that role, with Galen release manager for 3.1 (which will become
> > 3.2 when its stable).
> >     
> As far as I know, the following people or groups have expressed
> willingness to maintain 3.0:
>
> - Josh, per the customary transition from 3.0 release manager.
> - BibLibre, in (I assume) the person of Paul or Henri-Damien.
>
> LibLime would support either option.  If Josh does it, he will have
> plenty of time to devote to it, as he will no longer have the full
> release manager responsibilities and is also looking to hand over the
> translation manager's portfolio to somebody else.  If I remember
> correctly, Henri has also expressed willingness to be the QA manager
> for 3.2.  Because of the potential workload, if BibLibre were to also
> take up 3.0 RMaint, I'd ask to them to confirm whether they're willing
> to do both, giving proper attention to each.  If not, then either the
> 3.0 RMaint should default to Josh or we should put out another call
> for 3.2 QA.
>   
As far as we (BibLibre) are concerned, even though it was talked about
a while back, we are in fact not candidate for the QA management
position in 3.2. So the position is indeed open: anyone volunteering ?

But I'm really willing to be Release Maintainer for 3.0.
We fully support what Chris said about the roles being spread around as many 
organisations as possible.
By the same token we support his candidacy to be the translation manager.

But I also think we should be clear about what those positions would mean.
Specifically, these roles (Q&A, RM for 3.1, RMaint for 3.0,
Translation) should have ssh access to the git repository via a key so
that they can do what their position requires them to do, with
sign-off of their commits so that RM can be informed in real time of
what has been done.

--
Henri-Damien LAURENT