On Saturday 14 April 2012 08:37:25 Cyrille Berger Skott wrote: > On Thursday 12 Apr 2012, Jaroslaw Staniek wrote: > > Isn't that used as: FEATURE: <wish number> ? > > I had forgotten about that. What about either: > > FEATURE/BUG: <wish number> > DESCRIPTION: optional description that overide the title from bug (usefull > when bug report have bad titles like "crash in APPNAME" > > Or: > > FEATURE/BUG: description when there is no bug 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. > > Personnaly, that is how I work with most non-kde projects. But I am unsure > about enforcing that, unless bugs.kde.org user experience has improved > drastically. I don't wan't to enforce opening wishes for features. In fact I rather dislike wishes in the bugtracker.
So my vote is for: FEATUREINFO: description _______________________________________________ calligra-devel mailing list calligra-devel@kde.org https://mail.kde.org/mailman/listinfo/calligra-devel
