Using Github issues is already a standard now, for reference this was the
voting thread:
https://markmail.org/message/y5zgkssmwp4sh43t
I agree that Github milestone tagging on a pull request is limited to one per
PR which I don't like as well. However, there is a workaround that may be
+1 as a new developer for this community, I find Github much easier for me to
create/track both issues and PRs.
From: Will Stevens
Sent: Thursday, July 19, 2018 3:35:00 AM
To: dev@cloudstack.apache.org
Cc: users
Subject: Re: Github Issues
Github is the
; project are doing. The bad thing here is that you might end up with
> too
> > > > many labels. Maybe @resmo can give his point of view on how things
> are
> > > > managed in Ansible (https://github.com/ansible/ansible/pulls - lots
> of
> > > > labels, lots of
gt; > > project are doing. The bad thing here is that you might end up with too
> > > many labels. Maybe @resmo can give his point of view on how things are
> > > managed in Ansible (https://github.com/ansible/ansible/pulls - lots of
> > > labels, lots of issues an
Ansible (https://github.com/ansible/ansible/pulls - lots of
> > labels, lots of issues and PRs). I don't know if that's a solution but
> > labels seem the only way to organize things.
>
> Personally, I don't care much if jira or github issues. Github issues
>
give his point of view on how things are
> managed in Ansible (https://github.com/ansible/ansible/pulls - lots of
> labels, lots of issues and PRs). I don't know if that's a solution but
> labels seem the only way to organize things.
Personally, I don't care much if jira or github
I sort of agree with Marc-Aurèle and Will, and like github issues way
better than Jira.
It definitely is easier that both the issues and fix for those issues live
in the same place
and easily can be referenced from one another. The only thing is that we
need to come
up with good set of labels
uld
> recognize while PRs are most often described as what was done to fix the
> problem. The JIRA could be much easier to relate to what the user is
> seeing and more likely to show up in Google.
>
> Ron
> On 17/07/2018 4:53 AM, Paul Angus wrote:
> > Hi All,
> >
> >
Github Issues. I think that we
should have a conversation about it before it become the new standard by
default.
From my perspective, I don't like it. Searching has become far more
difficult, categorising has also. When there is a bug fix it can only be
targeted for a single version,
#x27;s a solution but
labels seem the only way to organize things.
Marc-Aurèle
On Tue, Jul 17, 2018 at 10:53 AM, Paul Angus
wrote:
> Hi All,
>
> We have been trialling replacing Jira with Github Issues. I think that
> we should have a conversation about it before it beco
Hi All,
We have been trialling replacing Jira with Github Issues. I think that we
should have a conversation about it before it become the new standard by
default.
From my perspective, I don't like it. Searching has become far more difficult,
categorising has also. When there is a bu
Enabled for your repos: https://issues.apache.org/jira/browse/INFRA-16186
Cheers
On Mon, Apr 2, 2018 at 1:23 PM, Rohit Yadav wrote:
> Ping infra?
>
> - Rohit
>
> On Fri, Mar 30, 2018 at 1:51 PM, Rohit Yadav wrote:
>>
>> All,
>>
>> Based on a vote [1] on Apache CloudStack MLs, I would like to re
Ping infra?
- Rohit
On Fri, Mar 30, 2018 at 1:51 PM, Rohit Yadav wrote:
> All,
>
> Based on a vote [1] on Apache CloudStack MLs, I would like to request
> infra to enable Github issue and wiki features for all cloudstack
> repositories:
>
> https://github.com/apache?q=cloudstack+
>
> [1] https:
for Android<https://aka.ms/ghei36>
>
>
> From: Rafael Weingärtner
> Sent: Friday, March 30, 2018 4:53:57 PM
> To: dev
> Subject: Re: [VOTE] Move to Github issues
>
> Awesome Rohit.Can you also ask Infra to enable Wiki? Then, we could al
Rafael, yes I did see the other email to infra cc-ed to dev@. I've also
reopened a ticket.
Get Outlook for Android<https://aka.ms/ghei36>
From: Rafael Weingärtner
Sent: Friday, March 30, 2018 4:53:57 PM
To: dev
Subject: Re: [VOTE] Move to Github issu
e Github features for us, and
> update the website/docs over the next few days.
>
> After issues is available, users should use Github issues for logging
> bugs/features etc. Developers who have submitted PRs without a jira id may
> be accepted now provided their PRs have a mileston
All,
Based on a vote [1] on Apache CloudStack MLs, I would like to request infra
to enable Github issue and wiki features for all cloudstack repositories:
https://github.com/apache?q=cloudstack+
[1] https://markmail.org/message/y5zgkssmwp4sh43t
Regards,
Rohit Yadav
PMC member and committer,
Apa
Thanks all, after 5days the vote *passes* with all in favour of the proposal.
I'll request infra immediately to enable the Github features for us, and update
the website/docs over the next few days.
After issues is available, users should use Github issues for logging
bugs/feature
+1
On 3/26/18, 12:33 AM, "Rohit Yadav" wrote:
All,
Based on the discussion last week [1], I would like to start a vote to put
the proposal into effect:
- Enable Github issues, wiki features in CloudStack repositories.
- Both user and developers can
> From: David Mabry
> Sent: Monday, 26 March 2018 4:51 PM
> To: dev@cloudstack.apache.org
> Cc: users
> Subject: Re: [VOTE] Move to Github issues
>
> +1
>
> On 3/26/18, 8:05 AM, "Will Stevens" wrote:
>
> +1
>
> On Mon, Mar 26, 2018
: Re: [VOTE] Move to Github issues
+1
On 3/26/18, 8:05 AM, "Will Stevens" wrote:
+1
On Mon, Mar 26, 2018, 5:51 AM Nicolas Vazquez, <
nicolas.vazq...@shapeblue.com> wrote:
> +1
>
>
> From: Dag
ch 26, 2018 5:06:29 AM
> To: us...@cloudstack.apache.org; dev@cloudstack.apache.org
> Subject: Re: [VOTE] Move to Github issues
>
> +1
>
> Regards,
> Dag Sonstebo
> Cloud Architect
> ShapeBlue
>
> On 26/03/2018, 07:33, &qu
Sent: Monday, March 26, 2018 5:06:29 AM
> > To: us...@cloudstack.apache.org; dev@cloudstack.apache.org
> > Subject: Re: [VOTE] Move to Github issues
> >
> > +1
> >
> > Regards,
> > Dag Sonstebo
> > Cloud Architect
> > ShapeBlue
> >
> > On 26/0
Sent: Monday, March 26, 2018 5:06:29 AM
> > To: us...@cloudstack.apache.org; dev@cloudstack.apache.org
> > Subject: Re: [VOTE] Move to Github issues
> >
> > +1
> >
> > Regards,
> > Dag Sonstebo
> > Cloud Architect
> > ShapeBlue
> >
> > On 26/03/2
+1 (binding).
From: Rohit Yadav
Sent: Monday, March 26, 2018 1:33 AM
To: dev@cloudstack.apache.org; us...@cloudstack.apache.org
Subject: [VOTE] Move to Github issues
All,
Based on the discussion last week [1], I would like to start a vote to put
the proposal
Sent: Monday, March 26, 2018 5:06:29 AM
> > To: us...@cloudstack.apache.org; dev@cloudstack.apache.org
> > Subject: Re: [VOTE] Move to Github issues
> >
> > +1
> >
> > Regards,
> > Dag Sonstebo
> > Cloud Architect
> > ShapeBlue
> >
> > On 26/03/2
: Re: [VOTE] Move to Github issues
>
> +1
>
> Regards,
> Dag Sonstebo
> Cloud Architect
> ShapeBlue
>
> On 26/03/2018, 07:33, "Rohit Yadav" wrote:
>
> All,
>
> Based on the discussion last week [1], I would like to start a vote to
> put
&
+1
From: Dag Sonstebo
Sent: Monday, March 26, 2018 5:06:29 AM
To: us...@cloudstack.apache.org; dev@cloudstack.apache.org
Subject: Re: [VOTE] Move to Github issues
+1
Regards,
Dag Sonstebo
Cloud Architect
ShapeBlue
On 26/03/2018, 07:33, "Rohit Yadav&qu
a vote to
> put
> the proposal into effect:
>
> - Enable Github issues, wiki features in CloudStack repositories.
> - Both user and developers can use Github issues for tracking issues.
> - Developers can use #id references while fixing an existing/open
> issue
+1
Regards,
Dag Sonstebo
Cloud Architect
ShapeBlue
On 26/03/2018, 07:33, "Rohit Yadav" wrote:
All,
Based on the discussion last week [1], I would like to start a vote to put
the proposal into effect:
- Enable Github issues, wiki features in CloudStack re
-- Original Message -
>> From: "Rohit Yadav"
>> To: "dev" , "users"
>> Sent: Monday, 26 March, 2018 07:33:08
>> Subject: [VOTE] Move to Github issues
>
>> All,
>>
>> Based on the discussion last week [1], I wo
+1
--
Sent from the Delta quadrant using Borg technology!
Nux!
www.nux.ro
- Original Message -
> From: "Rohit Yadav"
> To: "dev" , "users"
> Sent: Monday, 26 March, 2018 07:33:08
> Subject: [VOTE] Move to Github issues
> All,
>
>
+1
+1
On 03/26/2018 08:33 AM, Rohit Yadav wrote:
> All,
>
> Based on the discussion last week [1], I would like to start a vote to put
> the proposal into effect:
>
> - Enable Github issues, wiki features in CloudStack repositories.
> - Both user and developers can use Githu
All,
Based on the discussion last week [1], I would like to start a vote to put
the proposal into effect:
- Enable Github issues, wiki features in CloudStack repositories.
- Both user and developers can use Github issues for tracking issues.
- Developers can use #id references while fixing an
35 matches
Mail list logo
