juneau-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "John D. Ament" <johndam...@apache.org>
Subject Re: [VOTE] - Which bug tracking system should we be using.
Date Tue, 28 Jun 2016 14:00:02 GMT
James,

I just want to make sure we're level setting here.  GitHub issues is not an
option right now.  We can poll infra to see when it is an option, but right
now its not.

John

On Tue, Jun 28, 2016 at 9:56 AM James Bognar <james.bognar@salesforce.com>
wrote:

> Our choices are....
>
> - Bugzilla
> - Jira
> - GitHub Issues
>
> Jira is officially supported by ASF and a Jira repository has already been
> set up.  However, GitHub issues is also allowed and may be simpler to use
> and more commonly used in the future.  Bugzilla is slowly going away.
>
> To vote, put [-1](opposed), [0] (no preference), or [1](support) next to
> each choice...
>
> My vote...
> - Bugzilla [-1]
> - Jira [0]
> - GitHub Issues [0]
>
>
> On Tue, Jun 28, 2016 at 9:51 AM, James Bognar <james.bognar@salesforce.com
> >
> wrote:
>
> > My vote:
> >
> > [0] - No preference either way.
> >
> > On Tue, Jun 28, 2016 at 9:50 AM, Jochen Wiedmann <
> > jochen.wiedmann@gmail.com> wrote:
> >
> >> It's definitely a matter of preference. How about a vote?
> >>
> >>
> >> On Tue, Jun 28, 2016 at 3:47 PM, James Bognar
> >> <james.bognar@salesforce.com> wrote:
> >> > My $.02.
> >> >
> >> > Using GitHub Issues sounds appealing.  But something feels strange
> about
> >> > using GitHub for bugs but not SCM.
> >> >
> >> > I'm leaning slightly towards using GitHub Issues.  GitHub seems to be
> >> > taking over the world.  But I don't feel strongly about it since I'm
> >> really
> >> > unfamiliar with either right now.  I'll be okay with whatever the
> >> community
> >> > decides.
> >> >
> >> >
> >> > ---------- Forwarded message ----------
> >> > From: Stian Soiland-Reyes <stain@apache.org>
> >> > Date: Tue, Jun 28, 2016 at 9:05 AM
> >> > Subject: Re: Juneau Project Bootstrap
> >> > To: private@juneau.incubator.apache.org
> >> > Cc: Peter Haumer <phaumer@us.ibm.com>, "craig.russell@oracle.com"
<
> >> > craig.russell@oracle.com>, Craig Chaney <cchaney@salesforce.com>,
> >> "John D.
> >> > Ament" <johndament@apache.org>, James Bognar <
> >> james.bognar@salesforce.com>,
> >> > david.goddard@uk.ibm.com, Brian Laskey <blaskey@us.ibm.com>, Min
> >> Idzelis <
> >> > midzelis@salesforce.com>
> >> >
> >> >
> >> > Let's continue this discussion on dev@juneau.incubator.apache.org.
> >> (you can
> >> > sign up before you have signed ICLA and get @apache.org address)
> >> >
> >> > On 28 Jun 2016 6:46 a.m., "Jochen Wiedmann" <
> jochen.wiedmann@gmail.com>
> >> > wrote:
> >> >
> >> >>
> >> >>
> >> >> On Mon, Jun 27, 2016 at 10:45 PM, Peter Haumer <phaumer@us.ibm.com>
> >> wrote:
> >> >>
> >> >>> Hello.
> >> >>> Speaking of tools, can we continue developing on GitHub and then
> push
> >> >>> commits over in batch to the Apache Git for releases?
> >> >>>
> >> >>> I see on the incubator page that there is an entry for using JIRA,
> >> which
> >> >>> is a commercially licensed product and a direct competitor to the
> >> product
> >> >>> in which this library was originally developed. Is using that really
> >> >>> required or can we continue with GitHub issues as well?
> >> >>>
> >> >>> AFAIK, Infra is still only supporting ASF Git as the primary
> >> repository,
> >> >> and Git as a mirror. I believe, this is, what John requested.
> >> >>
> >> >> I think, this means, that you will be required to download pull
> >> requests
> >> >> from GitHub as a file before applying them. However, that
> inconvenience
> >> >> should be acceptable, IMO.
> >> >>
> >> >> As an exception from that rule. I have read, just yesterday, that it
> >> >> should now be acceptable, if Juneau decides *not* to use the ASF Jira
> >> for
> >> >> bug reports, and use GitHub issues instead. My personal impression
> is,
> >> that
> >> >> this wouldn't really be an advantage, because tool support for Jira
> is
> >> much
> >> >> better than for Github. OTOH, GitHub might be more attractive for
> >> users.
> >> >>
> >> >> Again, John should be able to tell about details.
> >> >>
> >> >> Jochen
> >> >>
> >> >>
> >> >>
> >> >>
> >> >> --
> >> >> The next time you hear: "Don't reinvent the wheel!"
> >> >>
> >> >>
> >> >>
> >>
> http://www.keystonedevelopment.co.uk/wp-content/uploads/2014/10/evolution-of-the-wheel-300x85.jpg
> >> >>
> >> >>
> >> >
> >> >
> >> > --
> >> > James Bognar
> >>
> >>
> >>
> >> --
> >> The next time you hear: "Don't reinvent the wheel!"
> >>
> >>
> >>
> http://www.keystonedevelopment.co.uk/wp-content/uploads/2014/10/evolution-of-the-wheel-300x85.jpg
> >>
> >
> >
> >
> > --
> > James Bognar
> >
>
>
>
> --
> James Bognar
>

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