ul.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.
If someone wants to know what versions a f
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, "Ron Wheeler&qu
of text...
>>
>> On Jun 30, 2017 6:52 AM, "Alex Hitchins" <a...@alexhitchins.com> wrote:
>>
>> Hello,
>>
>> I've created a DISCUSS thread to... discuss this subject separately from
>> the original Jira issue.
>>
>> Sorry Paul for hija
fael 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 directed to projects at
the donati
art...@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 knows about
-
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 directed
@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
gt; Marty Godsey
> Principal 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
>
&g
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
ed?
>
> Regards,
> 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
>
>
sage-
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.
Similar
ommunication 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 [mailto:daan.hoogl...@gmail.com]
Sent: 29 June 2017 10:14
T
t;>>> I think duplicating data between jira and the PR is kind of pointless. I
>>>> feel like the github PRs and the cide going in should be the source of
>>>> truth, not a random third party tool.
>>>>
>>>> For the 4.9 release notes, i built a
From: Daan Hoogland [mailto:daan.hoogl...@gmail.com]
Sent: 29 June 2017 10:14
To: dev <dev@cloudstack.apache.org>
Subject: Re: JIRA - PLEASE READ
On Thu, Jun 29, 2017 at 11:06 AM, Paul Angus <paul.an...@shapeblue.com>
wrote:
+ Release notes will be impossible to create without a pro
, June 29, 2017 9:42 AM
To: Ron Wheeler <rwhee...@artifact-software.com>; 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
tops users/operators from having any chance of 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,
>>
>> Pau
@shapeblue
-Original Message-
From: Daan Hoogland [mailto:daan.hoogl...@gmail.com]
Sent: 29 June 2017 10:14
To: dev <dev@cloudstack.apache.org>
Subject: Re: JIRA - PLEASE READ
On Thu, Jun 29, 2017 at 11:06 AM, Paul Angus <paul.an...@shapeblue.com>
wrote:
+ Release notes wi
;
> >
> >
> > -Original Message-
> > From: Daan Hoogland [mailto:daan.hoogl...@gmail.com]
> > Sent: 29 June 2017 10:14
> > To: dev <dev@cloudstack.apache.org>
> > Subject: Re: JIRA - PLEASE READ
> >
> >> On Thu, Jun 29, 2
m: Daan Hoogland [mailto:daan.hoogl...@gmail.com]
Sent: 29 June 2017 10:14
To: dev <dev@cloudstack.apache.org>
Subject: Re: JIRA - PLEASE READ
On Thu, Jun 29, 2017 at 11:06 AM, Paul Angus <paul.an...@shapeblue.com>
wrote:
> + Release notes will be impossible to create without a pr
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
dos 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 <dev@cloudstack.apache.org>
> Subject: Re: JIRA - PLEASE READ
>
>>
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 <dev@cloudstack.apache.org>
Subject: Re: JIRA - PLEAS
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
23 matches
Mail list logo