[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [gef-dev] New GEF build requires standard for commit comments
|
Ian:
"NEW" and "bug" provide no information. The link, while handy if
viewed in a clickable UI, also provides no more information (beyond
the number itself). And the bug summary (title) can be extracted from
Bugzilla via its web API, so all I need is that the comment starts
with the bug number, eg "[123456] some comment".
Mylyn can be configured so its comment template starts with
"[${task.id}] " and then whatever you'd like to follow it with, be it
the bug title, status, author, cvs branch, etc. (All of which is
already in CVS or Bugzilla, but you may have other reasons for wanting
to provide that information in duplicate.)
Note also that if you're working on multiple task contexts / bugs
concurrently (or a fix applies to more than one bug), Mylyn will list
the pertinent bugs one-per-line, which will *also* work with the
Release Notes generator -- again, provided that each bug is on its own
line, prefixed with "[234567]"
For more information, see:
http://wiki.eclipse.org/Modeling_Project_Releng/Releasing#Generating_Release_Notes
Cheers,
Nick
On 1/11/08, Ian Bull <irbull@xxxxxxxxxx> wrote:
> Nick, does the commit comment have to start with the task in square
> brackets, or can it be anywhere in the comment:
>
> i.e. can I use:
>
> NEW - bug [213057]: Layout filter does not expose the necessary API
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=213057
>
> Since this is pretty much the default mylyn commit comment.
>
> cheers,
> ian
>
> Anthony Hunter wrote:
> > Hi Team,
> >
> > Nick is working on a moving the GEF build to the standard modeling set of
> > scripts. The scripts produce release notes indicating what has been fixed
> > in this build.
> >
> > Going forward, each delivery/commit to CVS requires a Bugzilla and the
> > Bugzilla number needs to be in the commit comment in square brackets
> >
> > I.e. Bugzilla 129188
> >
> > Commit comment:
> >
> > [129188] Should be able to remove borders
> >
> > Cheers...
> > Anthony
