~alpine/devel

2 2

[alpine-devel] New role for maintainers in bugs.a.o

Natanael Copa <ncopa@alpinelinux.org>
Details
Message ID
<20120119085504.6996ba5c@ncopa-desktop.nor.wtbts.net>
Sender timestamp
1326959704
DKIM signature
missing
Download raw message
Hi,

I have added a new role: "Aports Maintainers" to bugs.a.o. It is
mainly because I need to be able to assigns issues to the maintainers.

I am not completely sure how to do the maintainer workflow, but I think
something like this:

1. a bug report is created
2. the maintainer gets assigned
3. the maintainer fix it and creates a patch
4. a developer commits it

The patch can/should include "fixes #NNN"  in the commit message if it
fixes the issue or "ref #NNN" if it is related an issue.

This also means, to become an aports maintainer you need a login on
bugs.a.o and you need to be assigned the role "Aports Maintainer"

I am open for ideas and suggestions.

Thanks!

 -nc


---
Unsubscribe:  alpine-devel+unsubscribe@lists.alpinelinux.org
Help:         alpine-devel+help@lists.alpinelinux.org
---
Jeremy Thomerson <jeremy@thomersonfamily.com>
Details
Message ID
<CADVmKVBLk5kz0x-0UnoEpFNxsCvkcCYsLPtr1+j1GOOwyo36hQ@mail.gmail.com>
In-Reply-To
<20120119085504.6996ba5c@ncopa-desktop.nor.wtbts.net> (view parent)
Sender timestamp
1326978336
DKIM signature
missing
Download raw message
On Thu, Jan 19, 2012 at 2:55 AM, Natanael Copa <ncopa@alpinelinux.org>wrote:

> Hi,
>
> I have added a new role: "Aports Maintainers" to bugs.a.o. It is
> mainly because I need to be able to assigns issues to the maintainers.
>
> I am not completely sure how to do the maintainer workflow, but I think
> something like this:
>
> 1. a bug report is created
> 2. the maintainer gets assigned
> 3. the maintainer fix it and creates a patch
> 4. a developer commits it
>

Works for me.  Do I need to do anything special to get email notification
of tickets that are assigned to me (since I don't regularly read bugs.a.o)?


> The patch can/should include "fixes #NNN"  in the commit message if it
> fixes the issue or "ref #NNN" if it is related an issue.
>
> This also means, to become an aports maintainer you need a login on
> bugs.a.o and you need to be assigned the role "Aports Maintainer"
>

Please add: jrthomerson

--
Jeremy Thomerson
Natanael Copa <ncopa@alpinelinux.org>
Details
Message ID
<20120119141715.22e258ad@ncopa-desktop.nor.wtbts.net>
In-Reply-To
<CADVmKVBLk5kz0x-0UnoEpFNxsCvkcCYsLPtr1+j1GOOwyo36hQ@mail.gmail.com> (view parent)
Sender timestamp
1326979035
DKIM signature
missing
Download raw message
On Thu, 19 Jan 2012 08:05:36 -0500
Jeremy Thomerson <jeremy@thomersonfamily.com> wrote:

> On Thu, Jan 19, 2012 at 2:55 AM, Natanael Copa
> <ncopa@alpinelinux.org>wrote:
> 
> > Hi,
> >
> > I have added a new role: "Aports Maintainers" to bugs.a.o. It is
> > mainly because I need to be able to assigns issues to the
> > maintainers.
> >
> > I am not completely sure how to do the maintainer workflow, but I
> > think something like this:
> >
> > 1. a bug report is created
> > 2. the maintainer gets assigned
> > 3. the maintainer fix it and creates a patch
> > 4. a developer commits it
> >
> 
> Works for me.  Do I need to do anything special to get email
> notification of tickets that are assigned to me (since I don't
> regularly read bugs.a.o)?

On your profile the "Email notification" setting is currently set to
"Only for things I watch or are involved with"

So you are supposed to get email notifications for things that gets
assigned to you, and things you comment on etc.
 
> > The patch can/should include "fixes #NNN"  in the commit message if
> > it fixes the issue or "ref #NNN" if it is related an issue.
> >
> > This also means, to become an aports maintainer you need a login on
> > bugs.a.o and you need to be assigned the role "Aports Maintainer"
> >
> 
> Please add: jrthomerson

done. Thanks!

-nc


---
Unsubscribe:  alpine-devel+unsubscribe@lists.alpinelinux.org
Help:         alpine-devel+help@lists.alpinelinux.org
---
Reply to thread Export thread (mbox)