drill-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Kamesh <kamesh.had...@gmail.com>
Subject Re: Improved JIRA process
Date Wed, 23 Sep 2015 02:35:34 GMT
+1 on this proposal.

On Wed, Sep 23, 2015 at 7:28 AM, Edmon Begoli <ebegoli@gmail.com> wrote:

> Got it. Makes sense.
>
> On Tue, Sep 22, 2015 at 9:42 PM, Jacques Nadeau <jacques@dremio.com>
> wrote:
>
> > On (3), my thought is that they plan on commencing in the next couple
> > weeks, (not that they have to complete by then). The fix for tag tells
> > others how long they it will take. If someone wants it faster, they
> should
> > chime in to help out.
> >
> > --
> > Jacques Nadeau
> > CTO and Co-Founder, Dremio
> >
> > On Tue, Sep 22, 2015 at 6:15 PM, Edmon Begoli <ebegoli@gmail.com> wrote:
> >
> > > Sounds good to me.
> > >
> > > I would only comment that we should probably relax item 3 to tie the
> > > commitment to the release schedule.
> > > There might be issues that cannot be worked on within few weeks, but
> are
> > > good to keep planned for the future few releases ahead.
> > >
> > > On Tue, Sep 22, 2015 at 9:05 PM, Jacques Nadeau <jacques@apache.org>
> > > wrote:
> > >
> > > > Hey Everybody,
> > > >
> > > > As more and more people are starting to work on JIRAs, I'd like to
> > > propose
> > > > a new process around jira assignment, targeting, etc. This way people
> > > will
> > > > be able to more easily identify available issues for pick up and
> > general
> > > > development intentions.
> > > >
> > > > I propose the following:
> > > >
> > > >    1. We should remove the default assignment of new issues.
> > > >    2. We need to remove all current assignments other than those that
> > are
> > > >    currently active (or about to be active).
> > > >    3. Individual developers who plan to work on a feature should
> assign
> > > it
> > > >    to themselves. This should be a commitment to work on this feature
> > > > within
> > > >    the next couple weeks. (They should also set the "fix for" to the
> > > > release
> > > >    they would like to target completion.)
> > > >    4. Once a developer starts work on a feature, they should accept
> the
> > > >    feature (showing that they are actively working on it).
> > > >    5. If another developer is interested in working on a feature that
> > is
> > > >    assigned (but inactive), they should request taking over that
> > feature
> > > > from
> > > >    the current assignee.
> > > >
> > > > How does this sound?
> > > >
> > > > Jacques
> > > >
> > >
> >
>



-- 
Kamesh.

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message