KDE git workflow

[C. Boemann]

On Wednesday 08 June 2011 23:01:13 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 from the integration branch (once there is one) to master when it
> brings down the number of problems found by automated testing.
> 
> Cheers,
> Jos
> 
> _______________________________________________
> calligra-devel mailing list
> calligra-devel at kde.org
> https://mail.kde.org/mailman/listinfo/calligra-devel
Well that is part of the plan we have so i don't think you'll have any  
disagreement there

but automated testing alone is not the answer. tests can be wrong too or 
changed wrongly. So it's upon us all to just be more diligent (i know i need 
to improve and i really plan to, but right now speedy work on words is more 
important) Besides Pierre Ducroquet have been doing really great work on 
automating the unit testing of styles loading and saving. And once the 
textlayout is like close to what we want it to be. This should be thoroughly 
unit tested too. It's high on my todo list. (not that we don't have tests now 
and that they don't catch stuff now and then, but they could still be improved 
hugely)