[DISCUSS] Using JIRA for Release Mgmt / GitHub for Issues

[Brian Spector <br...@qredo.com>]

Hi All,

John and I have been thinking that the best way to manage the multiple 
libraries and products that we want to release that are coming down the 
pike is to manage the release process centrally in the JIRA issue 
tracker that has already been setup. That way in can span across repos. 
The release process is super involved, and for the time being we will be 
doing it manually. Keeping track of all issues centrally outside of the 
general development issues that can be put into GitHub issues on the 
individual repo seems to make the most sense.

We will still move to tracking development issues on GitHub as 
previously planned and as Kealan and Giorgio have already started doing.

Are there any objections or gotchas that should be aired before we start 
down this road?

Thanks
Brian

Re: [DISCUSS] Using JIRA for Release Mgmt / GitHub for Issues

[Giorgio Zoppi <gi...@gmail.com>]

Agree.

On Wed, Jun 26, 2019, 12:45 John McCane-Whitney <jo...@qredo.com> wrote:

> Hi everyone,
>
> Thanks Brian - this makes sense to me.
>
> Regards,
>
> John
>
> -----Original Message-----
> From: Brian Spector <br...@qredo.com>
> Sent: 26 June 2019 11:42
> To: dev@milagro.apache.org
> Subject: [DISCUSS] Using JIRA for Release Mgmt / GitHub for Issues
>
> Hi All,
>
> John and I have been thinking that the best way to manage the multiple
> libraries and products that we want to release that are coming down the
> pike
> is to manage the release process centrally in the JIRA issue tracker that
> has
> already been setup. That way in can span across repos.
> The release process is super involved, and for the time being we will be
> doing
> it manually. Keeping track of all issues centrally outside of the general
> development issues that can be put into GitHub issues on the individual
> repo
> seems to make the most sense.
>
> We will still move to tracking development issues on GitHub as previously
> planned and as Kealan and Giorgio have already started doing.
>
> Are there any objections or gotchas that should be aired before we start
> down
> this road?
>
> Thanks
> Brian
>
>

RE: [DISCUSS] Using JIRA for Release Mgmt / GitHub for Issues

[John McCane-Whitney <jo...@qredo.com>]

Hi everyone,

Thanks Brian - this makes sense to me.

Regards,

John

-----Original Message-----
From: Brian Spector <br...@qredo.com>
Sent: 26 June 2019 11:42
To: dev@milagro.apache.org
Subject: [DISCUSS] Using JIRA for Release Mgmt / GitHub for Issues

Hi All,

John and I have been thinking that the best way to manage the multiple 
libraries and products that we want to release that are coming down the pike 
is to manage the release process centrally in the JIRA issue tracker that has 
already been setup. That way in can span across repos.
The release process is super involved, and for the time being we will be doing 
it manually. Keeping track of all issues centrally outside of the general 
development issues that can be put into GitHub issues on the individual repo 
seems to make the most sense.

We will still move to tracking development issues on GitHub as previously 
planned and as Kealan and Giorgio have already started doing.

Are there any objections or gotchas that should be aired before we start down 
this road?

Thanks
Brian