Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 03 Aug 2014 17:40:35 -0700
From:      Craig Leres <leres@ee.lbl.gov>
To:        Matthew Seaman <m.seaman@infracaninophile.co.uk>, freebsd-ports@freebsd.org
Subject:   Re: How do maintainer updates work with bugzilla?
Message-ID:  <53DED683.9020306@ee.lbl.gov>
In-Reply-To: <53DE8AF1.6070206@infracaninophile.co.uk>
References:  <53DE72E1.1010005@ee.lbl.gov> <53DE8AF1.6070206@infracaninophile.co.uk>

next in thread | previous in thread | raw e-mail | index | archive | help
On 08/03/14 12:18, Matthew Seaman wrote:
> I take it you mean PR 192105 ?

(Sorry, I meant to include a link to the PR.)

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192105

> By virtue of sending a PR into the system a leres@ee.lbl.gov account
> will have been created in Bugzilla.  You should be able to use the
> 'Forgot Password' link to set a password on that account, then log in
> and add a flag to the attached diff to say 'maintainer approved'.

I was able to access my bugzilla account back when I created the PR.

I assume setting a '+' flag on the attachment means I approve it.

> Once that's done it should get triaged and if you're lucky, set to
> 'Patch Ready' in which case someone with a commit bit can go ahead and
> commit the update.

Triaged is something that an admin does manually?

> You'll help that to happen if you can supply a link to Redports or the
> output from 'poudriere testport' or similar showing that your update
> passes some sanity checks.  (It's not mandatory for PR submitters to
> supply this sort of testing output, but it pretty much is mandatory for
> all patches to be tested in this way before they are committed.  So if
> you do it yourself, you can make it quicker and easier for any committer
> to proceed.)

Redports looks pretty cool; I just updated the PR with build logs.

I appreciate your help.

		Craig





Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?53DED683.9020306>