cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Will Stevens <williamstev...@gmail.com>
Subject RE: JIRA - PLEASE READ
Date Thu, 29 Jun 2017 12:03:54 GMT
Why are we still using jira instead of the PRs for that communication? Can
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 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 tool to generate the release notes
from the PRs merged in that release. I think that is easier and more
accurate than depending on jira since it does not track the actual code
tree.

Thats my 0.02$.

On Jun 29, 2017 5:25 AM, "Paul Angus" <paul.angus@shapeblue.com> wrote:

Such a view of CloudStack is what holds CloudStack back.
It stops 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,

Paul Angus

paul.angus@shapeblue.com
www.shapeblue.com
53 Chandos Place, Covent Garden, London  WC2N 4HSUK
@shapeblue




-----Original Message-----
From: Daan Hoogland [mailto:daan.hoogland@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.angus@shapeblue.com>
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 the use of Jira but it is not required
for good coding practices and as we are not and will not function as a
corporation, jira is an extra for those that grave for it. not a
requirement.

--
Daan

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