KDE git workflow

Pierre Stirnweiss pstirnweiss at googlemail.com
Thu Jun 9 12:41:49 BST 2011


On Thu, Jun 9, 2011 at 1:13 PM, Cyrille Berger <cberger at cberger.net> wrote:

> On Wed, Jun 08, 2011 at 11:01:13PM +0200, Jos van den Oever wrote:
> > On Wednesday, June 08, 2011 21:18:49 PM Pierre Stirnweiss wrote:
> > > Well, sounds really really familiar. They could have attended our
> sprint
> > > and spared the discussion time, couldn't they? ;)
> > > IIRC this very workflow was already discussed in Oslo.
> >
> > I'll believe it when I see 0 failing tests and all document
> round-tripping
> > without errors. ;-)
> >
> > Seriously, I think we can get there if we set up a system where a patch
> can go
> We have discussed this at the last sprint in Berlin, the idea is that
> developers commit in master, and the buildbot validate the commits, and if
> the tests are passing they are migrated to a "master-validated" branch. And
> if master does not pass the test suite, the migration is blocked until the
> problem is solved, either by a fix, or by reverting the bad commit.
>
> And I am actually (slowly) working on the setup right now.
>

Any help needed in setting up a windows buildbot (if at all possible)?

Pierre
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/calligra-devel/attachments/20110609/9aa984a5/attachment.htm>


More information about the calligra-devel mailing list