commits to master

[Jaroslaw Staniek]

On 12 April 2012 14:50, Cyrille Berger <cberger at cberger.net> wrote:
> I have started to put together a draft of a commit policy:
>
> http://community.kde.org/Calligra/Policies/Commits
>
> For now, it is essentially what I said in my emails.
>
> For the git bisect part, maybe we could have some guideline on what to
> commit in branch,
> could be useful for beginners as well.
>
> As for the changelog, we can already make use of the "BUG" keyword. But
> what do you think of
> adding a FEATURE keyword, that would be followed by a description ? For
> instance:
>
> FEATURE: grammatical spell checking

Isn't that used as: FEATURE: <wish number> ?

Using this tag would mean that we start working on any nontrivial
feature by creating a wish for it (in JIRA it would be more naturally:
a task).
This requirement would be OK for me.

-- 
regards / pozdrawiam, Jaroslaw Staniek
 http://www.linkedin.com/in/jstaniek
 Kexi & Calligra (kexi-project.org, identi.ca/kexi, calligra-suite.org)
 KDE Software Development Platform on MS Windows (windows.kde.org)