Mailinglist Archive: opensuse-buildservice (366 mails)
| < Previous | Next > |
Re: [opensuse-buildservice] Random thought (CLI suggestion)
- From: JP Rosevear <jpr@xxxxxxxxxx>
- Date: Fri, 17 Aug 2007 13:38:17 -0400
- Message-id: <1187372298.5143.250.camel@xxxxxxxxxxxxxxxxxxxxx>
On Fri, 2007-08-17 at 15:41 +0200, Andrew Beekhof wrote:
> On Aug 16, 2007, at 4:54 PM, JP Rosevear wrote:
>
> > On Thu, 2007-08-16 at 14:26 +0200, Andrew Beekhof wrote:
> >> It occurred to me that a --populate-changelog option might be a
> >> useful addition to osc.
> >> Once commit messages are mandatory, I believe we would actually have
> >> enough information to implement this.
> >> It would also encourage better commit messages too!
> >>
> >> Would it be worth me putting together a patch to implement this?
> >
> > If you do, it would great to make it so you can pass bug number and it
> > pulls the summary or puts the bug in the changelog in some sort of
> > normalized form.
>
> In theory this might be a nice idea but its impractical - at least
> for the initial implementation.
>
> I work on heartbeat and we have bugs from our project's bugzilla,
> Novell's, Debian's, IBM's and SGI's (at least).
> So even just from a practical standpoint of deciding which bugzilla
> to connect to it would be a PITA.
Its not necessary to connect to a bugzilla for a first pass at least or
even normalize bugs outside of bnc, simply something like:
--populate-changelog --bug 290030 "pidgin requires NetworkManager"
would work - the key is that QA and others often have a difficult time
extracting what exactly went into each build. If the bug id's were
normalized some how, they would be easy to parse by perl or simple
scripts.
-JP
--
JP Rosevear <jpr@xxxxxxxxxx>
Novell, Inc.
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-buildservice+help@xxxxxxxxxxxx
> On Aug 16, 2007, at 4:54 PM, JP Rosevear wrote:
>
> > On Thu, 2007-08-16 at 14:26 +0200, Andrew Beekhof wrote:
> >> It occurred to me that a --populate-changelog option might be a
> >> useful addition to osc.
> >> Once commit messages are mandatory, I believe we would actually have
> >> enough information to implement this.
> >> It would also encourage better commit messages too!
> >>
> >> Would it be worth me putting together a patch to implement this?
> >
> > If you do, it would great to make it so you can pass bug number and it
> > pulls the summary or puts the bug in the changelog in some sort of
> > normalized form.
>
> In theory this might be a nice idea but its impractical - at least
> for the initial implementation.
>
> I work on heartbeat and we have bugs from our project's bugzilla,
> Novell's, Debian's, IBM's and SGI's (at least).
> So even just from a practical standpoint of deciding which bugzilla
> to connect to it would be a PITA.
Its not necessary to connect to a bugzilla for a first pass at least or
even normalize bugs outside of bnc, simply something like:
--populate-changelog --bug 290030 "pidgin requires NetworkManager"
would work - the key is that QA and others often have a difficult time
extracting what exactly went into each build. If the bug id's were
normalized some how, they would be easy to parse by perl or simple
scripts.
-JP
--
JP Rosevear <jpr@xxxxxxxxxx>
Novell, Inc.
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-buildservice+help@xxxxxxxxxxxx
| < Previous | Next > |