[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-release-team
Subject:    Re: Apologies for breaking the freeze and a suggestion
From:       Allen Winter <winter () kde ! org>
Date:       2012-07-12 20:24:02
Message-ID: 1487601.Hz3iIVoiVj () jiffy
[Download RAW message or body]

On Wednesday, July 11, 2012 11:23:28 AM Ben Cooksley wrote:
> On Wed, Jul 11, 2012 at 5:06 AM, Allen Winter <winter@kde.org> wrote:
> > On Tuesday, July 10, 2012 06:32:04 PM Aur=E9lien G=E2teau wrote:
> >> Hi,
> >> =

> >> This morning I worked on two bug fixes for Gwenview which I pushed to =
the
> >> KDE/4.9 branch. Only later in the afternoon did I check email and
> >> realized I should not have pushed those changes as we were freezing for
> >> RC2. I want to apologize for that.
> >> =

> >> Since a "git push" is a bit too easy to do, I was wondering whether it
> >> would be possible to have a git hook which would disallow pushing in
> >> freeze mode. The hook could be designed to only allow commits if they
> >> have a
> >> "APPROVED_BY_RELEASE_TEAM" keyword in the commit message.
> >> =

> >> This would prevent clueless people like me from pushing when they shou=
ld
> >> not. Do you think this is doable?
> > =

> > I don't know if it's doable.  But I like the idea.
> > =

> > Our awesome sysadmins might have some thoughts.
> =

> Whilst this would be possible, it would require maintaining a list of
> all KDE SC repositories which are affected by this freeze, and making
> changes around each freeze period to switch it on and off again.
> =


FYI:  Release Buddy has the ability to list the repos within KDE SC 4.9.
Here's how:
% git clone kde:release-buddy
% cd release-buddy
% ./buddy.py list kde-4.9.rc =


both git and svn repos are listed


_______________________________________________
release-team mailing list
release-team@kde.org
https://mail.kde.org/mailman/listinfo/release-team
[prev in list] [next in list] [prev in thread] [next in thread]