On Sun, 19 Jan 2014 04:10:20 -0500
Mike Frysinger wrote:
> i disagree. dev-portage@ get's cc-ed on bugs when they're being kept
> abreast of developments (like PMS), or someone just wants an
> opinion/feedback on an issue. so there's no way to differentiate
> between bugs that are assigned to t
On Tuesday 14 January 2014 21:58:38 Tom Wijsman wrote:
> On Sun, 05 Jan 2014 15:42:48 -0800 Brian Dolbec wrote:
> > 2) start working on a solution,
> >a) if you have significant progress, but need more time, mark it
> > accordingly, assign it to yourself, leave a comment, etc.
>
> Assign
On Sun, 05 Jan 2014 15:42:48 -0800
Brian Dolbec wrote:
> So, a suggested workflow is:
I like this workflow the most; however, feedback on it appears to be
missing and the document incorporation seems to outright ignore it.
Can we please (re)consider and discuss this?
> 1) check a bug,
> a
Here's a new version of the workflow that tries to incorporate
all the comments.
This should go into the DEVELOPING file once everyone agrees.
Bugzilla
There always exists a tracker bug, named:
"[Tracker] sys-apps/portage-".
This bug is renamed from X.Y.Z to X.Y.Z+1 after a release, un
On Sun, 2014-01-05 at 18:04 -0500, Mike Frysinger wrote:
> On Sunday 05 January 2014 17:54:12 Alexander Berntsen wrote:
> > On 05/01/14 23:30, Brian Dolbec wrote:
> > > If you open the tracker bug. The bug numbers listed as blockers.
> > > Hover your mouse over the bug number. A small popup windo
On Sunday 05 January 2014 17:54:12 Alexander Berntsen wrote:
> On 05/01/14 23:30, Brian Dolbec wrote:
> > If you open the tracker bug. The bug numbers listed as blockers.
> > Hover your mouse over the bug number. A small popup window
> > appears and shows the bug summary and status. The keywords
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 05/01/14 23:30, Brian Dolbec wrote:
> If you open the tracker bug. The bug numbers listed as blockers.
> Hover your mouse over the bug number. A small popup window
> appears and shows the bug summary and status. The keywords are not
> listed.
On Sunday 05 January 2014 17:05:04 Sebastian Luther wrote:
> For now I tried to handle bugs like Zac did. That is:
>
> There always exists a tracker bug, named:
> "[Tracker] sys-apps/portage-".
would be nice to start adding an alias field. this way you can do:
https://bugs.gentoo.org/sho
On Sun, 2014-01-05 at 23:19 +0100, Alexander Berntsen wrote:
> On 05/01/14 23:05, Sebastian Luther wrote:
> > I like this workflow because it makes it easy to see what has been
> > fixed since the last release. The only thing I have no use for, is
> > this InVCS keyword. I do not know what Zac us
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 05/01/14 23:05, Sebastian Luther wrote:
> I like this workflow because it makes it easy to see what has been
> fixed since the last release. The only thing I have no use for, is
> this InVCS keyword. I do not know what Zac used it for. Does
> an
Hi all,
since we're at documenting things, I wonder if we want to discuss and
document the bugzilla workflow.
For now I tried to handle bugs like Zac did. That is:
There always exists a tracker bug, named:
"[Tracker] sys-apps/portage-".
This bug is renamed from X.Y.Z to X.Y.Z+1 after a release,
11 matches
Mail list logo
