[prev in list] [next in list] [prev in thread] [next in thread]
List: kde-panel-devel
Subject: Re: Thoughts about a better Quality Management process for Plasma
From: Alex Fiestas <afiestas () kde ! org>
Date: 2013-01-14 15:21:04
Message-ID: 5491442.hF9DOaUBOe () monsterbad
[Download RAW message or body]
On Sunday 13 January 2013 15:50:25 Martin Gräßlin wrote:
> *Every commit should be referenced to a bug*
> What is the motivation for a commit? It's either a bug fix or it is a new
> feature/improvement. If it's a bug it's clear that there has to be a bug
> report for it (out of experience: there is always a bug, if not: create it).
> If it's a feature, it should also have a feature request in the tracker.
> Create it yourself if you need to. Sounds beaurocratic, but it comes quite
> handy as it allows to generate changelogs from it, allows people to easily
> test new features.Martin
In case of big features, I guess we could add the BUG in the commit made for
the merge right? Or you want exactly one commit for feature?
_______________________________________________
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic