RE: JIRA - PLEASE READ

2017-06-30 Thread Giles Sirett
aul Angus [mailto:paul.an...@shapeblue.com] Sent: 30 June 2017 16:34 To: dev@cloudstack.apache.org Subject: RE: JIRA - PLEASE READ Whether we use 'GitHub Issues' or 'Jira Issues' doesn't change the basic point, which is bug fixes and indeed features need to be tracked. I

RE: JIRA - PLEASE READ

2017-06-30 Thread Paul Angus
gmail.com] Sent: 30 June 2017 16:07 To: dev@cloudstack.apache.org Subject: Re: JIRA - PLEASE READ Yes, we would be adopting github issues for that then. If you want to handle those in jira we could, but i personally dont see any value in a jira ticket for an actual PR. On Jun 30, 2017 10:26 AM,

Re: JIRA - PLEASE READ

2017-06-30 Thread Will Stevens
2017 6:52 AM, "Alex Hitchins" wrote: >> >> Hello, >> >> I've created a DISCUSS thread to... discuss this subject separately from >> the original Jira issue. >> >> Sorry Paul for hijacking your Jira rant. >> >> >> Alexa

Re: JIRA - PLEASE READ

2017-06-30 Thread Ron Wheeler
ailto:rafaelweingart...@gmail.com] Sent: 29 June 2017 20:41 To: dev@cloudstack.apache.org Subject: Re: JIRA - PLEASE READ That is what I am saying. Apache can (and does) handle donations, and there have been discussions about donations that can be directed to projects at the donation time (someone that k

RE: JIRA - PLEASE READ

2017-06-30 Thread Will Stevens
29 June 2017 20:41 To: dev@cloudstack.apache.org Subject: Re: JIRA - PLEASE READ That is what I am saying. Apache can (and does) handle donations, and there have been discussions about donations that can be directed to projects at the donation time (someone that knows about the topic could provide

RE: JIRA - PLEASE READ

2017-06-30 Thread Alex Hitchins
ssage- From: Rafael Weingärtner [mailto:rafaelweingart...@gmail.com] Sent: 29 June 2017 20:41 To: dev@cloudstack.apache.org Subject: Re: JIRA - PLEASE READ That is what I am saying. Apache can (and does) handle donations, and there have been discussions about donations that can be direct

RE: JIRA - PLEASE READ

2017-06-30 Thread Giles Sirett
@shapeblue -Original Message- From: Alex Hitchins [mailto:a...@alexhitchins.com] Sent: 29 June 2017 18:49 To: dev@cloudstack.apache.org Subject: Re: JIRA - PLEASE READ If it isn't being treated as a product it will be very impossible to market it as enterprise ready. I know w

Re: JIRA - PLEASE READ

2017-06-29 Thread Rafael Weingärtner
cipal Engineer > nSource Solutions, LLC > > -Original Message- > From: Rafael Weingärtner [mailto:rafaelweingart...@gmail.com] > Sent: Thursday, June 29, 2017 3:28 PM > To: dev@cloudstack.apache.org > Subject: Re: JIRA - PLEASE READ > > ACS is an Apache project, no

RE: JIRA - PLEASE READ

2017-06-29 Thread Marty Godsey
elweingart...@gmail.com] Sent: Thursday, June 29, 2017 3:28 PM To: dev@cloudstack.apache.org Subject: Re: JIRA - PLEASE READ ACS is an Apache project, not a foundation per se; donation goes to Apache. I know that there is some discussion/work to create a way for donating things (not just money) to projects

Re: JIRA - PLEASE READ

2017-06-29 Thread Rafael Weingärtner
Marty Godsey > Principal Engineer > nSource Solutions, LLC > > -Original Message- > From: Alex Hitchins [mailto:a...@alexhitchins.com] > Sent: Thursday, June 29, 2017 1:49 PM > To: dev@cloudstack.apache.org > Subject: Re: JIRA - PLEASE READ > > If it isn'

RE: JIRA - PLEASE READ

2017-06-29 Thread Marty Godsey
l Message- From: Alex Hitchins [mailto:a...@alexhitchins.com] Sent: Thursday, June 29, 2017 1:49 PM To: dev@cloudstack.apache.org Subject: Re: JIRA - PLEASE READ If it isn't being treated as a product it will be very impossible to market it as enterprise ready. I know we all know this.

Re: JIRA - PLEASE READ

2017-06-29 Thread Ron Wheeler
and to everyone else. Kind regards, Paul Angus paul.an...@shapeblue.com www.shapeblue.com 53 Chandos Place, Covent Garden, London WC2N 4HSUK @shapeblue -Original Message- From: Daan Hoogland [mailto:daan.hoogl...@gmail.com] Sent: 29 June 2017 10:14 To: dev Subject: Re: JIRA - PLEASE

Re: JIRA - PLEASE READ

2017-06-29 Thread Alex Hitchins
gt;> we not use issues in github now instead of jira if someone needs to open >>>> an >>>> issue but does not yet have code to contribute. If not, jira could still >>>> be >>>> used for that. >>>> >>>> I think duplicating data be

Re: JIRA - PLEASE READ

2017-06-29 Thread Ron Wheeler
for code's sake is no use to anyone. Jira is about communication between developers and to everyone else. Kind regards, Paul Angus paul.an...@shapeblue.com www.shapeblue.com 53 Chandos Place, Covent Garden, London WC2N 4HSUK @shapeblue -Original Message----- From: Daan Hoogland [mai

RE: JIRA - PLEASE READ

2017-06-29 Thread Marty Godsey
, June 29, 2017 9:42 AM To: Ron Wheeler ; dev@cloudstack.apache.org Subject: Re: JIRA - PLEASE READ I personally don't know how Jira solves any of this, but assuming it does, fine... The bigger problem which you have raised is that CloudStack has zero funding. So we can't hire a

Re: JIRA - PLEASE READ

2017-06-29 Thread Will Stevens
understanding what >> CloudStack does and how it does it. >> Code for code's sake is no use to anyone. >> Jira is about communication between developers and to everyone else. >> >> >> >> Kind regards, >> >> Paul Angus >> >> paul.an

Re: JIRA - PLEASE READ

2017-06-29 Thread Ron Wheeler
al Message- From: Daan Hoogland [mailto:daan.hoogl...@gmail.com] Sent: 29 June 2017 10:14 To: dev Subject: Re: JIRA - PLEASE READ On Thu, Jun 29, 2017 at 11:06 AM, Paul Angus wrote: + Release notes will be impossible to create without a proper Jira history. And no one will know what has gone

Re: JIRA - PLEASE READ

2017-06-29 Thread Will Stevens
t; > > > > > Kind regards, > > > > Paul Angus > > > > paul.an...@shapeblue.com > > www.shapeblue.com > > 53 Chandos Place, Covent Garden, London WC2N 4HSUK > > @shapeblue > > > > > > > > > > -Original Message

RE: JIRA - PLEASE READ

2017-06-29 Thread Will Stevens
ilto:daan.hoogl...@gmail.com] Sent: 29 June 2017 10:14 To: dev Subject: Re: JIRA - PLEASE READ On Thu, Jun 29, 2017 at 11:06 AM, Paul Angus wrote: > + Release notes will be impossible to create without a proper Jira history. > And no one will know what has gone into CloudStack. No they are not m

Re: JIRA - PLEASE READ

2017-06-29 Thread Rene Moser
Hi Paul On 06/29/2017 11:06 AM, Paul Angus wrote: > Hi, Mr Grumpy here! > > I was looking the commits and I'm seeing commits going in with no Jira Issue > assigned. > My understanding is that there must be a Jira ticket for EVERY > fix/enhancement/feature, so that we have a way to search and

Re: JIRA - PLEASE READ

2017-06-29 Thread Alex Hitchins
WC2N 4HSUK > @shapeblue > > > > > -Original Message- > From: Daan Hoogland [mailto:daan.hoogl...@gmail.com] > Sent: 29 June 2017 10:14 > To: dev > Subject: Re: JIRA - PLEASE READ > >> On Thu, Jun 29, 2017 at 11:06 AM, Paul Angus >> wrote: &

RE: JIRA - PLEASE READ

2017-06-29 Thread Paul Angus
Paul Angus paul.an...@shapeblue.com  www.shapeblue.com 53 Chandos Place, Covent Garden, London WC2N 4HSUK @shapeblue -Original Message- From: Daan Hoogland [mailto:daan.hoogl...@gmail.com] Sent: 29 June 2017 10:14 To: dev Subject: Re: JIRA - PLEASE READ On Thu, Jun 29, 2017 at

Re: JIRA - PLEASE READ

2017-06-29 Thread Daan Hoogland
On Thu, Jun 29, 2017 at 11:06 AM, Paul Angus wrote: > + Release notes will be impossible to create without a proper Jira history. > And no one will know what has gone into CloudStack. No they are not mr Grumpy. they should be base on the code anyway, hence on git, not jira. I do not appose to th

JIRA - PLEASE READ

2017-06-29 Thread Paul Angus
Hi, Mr Grumpy here! I was looking the commits and I'm seeing commits going in with no Jira Issue assigned. My understanding is that there must be a Jira ticket for EVERY fix/enhancement/feature, so that we have a way to search and track these things. + Release notes will be impossible to cr