[Digikam-devel] separate branch for releases

sleepless sleeplessregulus at hetnet.nl
Mon Sep 19 20:00:46 BST 2011

Yes, might be a better idea than I had. Just test before upload. But not 
very usefull if it is uploaded while the tests are in progress. Maybe 
this works better.
Op 19-09-11 20:49, Veaceslav Munteanu schreef:
> Hello!
> When was the last release, everybody was told that 2 weeks before the 
> release, no features must be commited in branch master, only bugfixes.
> i thinks is not right to stop the development process and i have a 
> small suggestion:
> A month before release of certain version of digikam, to create a 
> separate branch, where only bugfixes and be applied.I don't know, 
> maybe to apply bugfixes on both master and new release branch and 
> delete the branch or simply to add bugfixes and merge the branch after 
> release.
> Also, branch can give us  more time for testing, so we could prevent 
> situations like these:
> https://bugs.kde.org/show_bug.cgi?id=281767
> and development process won't stop especially when you need to apply 
> fixes that depends on code that wasn't commited yet.
> What do you think?
> p.s. Idea was "stolen" from Karl Fogel's book, Producing Open Source 
> Software :)
> Best,
> -- 
> Veaceslav
> _______________________________________________
> Digikam-devel mailing list
> Digikam-devel at kde.org
> https://mail.kde.org/mailman/listinfo/digikam-devel

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/digikam-devel/attachments/20110919/0b0143ba/attachment.html>

More information about the Digikam-devel mailing list