JIRA issues typically remain open until the change has been resolved (as
there may be back-and-forth on code review for non-trivial changes).
Sit tight and Aaron (or whoever) will help close things up when it's
pulled in :)
Ben Kapp wrote:
Should I resolve this issue in Jira now that I have
Should I resolve this issue in Jira now that I have a pull request for it?
Or ought I wait until the pull request has been merged in?
On Fri, Dec 16, 2016 at 6:56 AM, Aaron D. Mihalik
wrote:
> John: Thanks for the catch and the pr!
>
> Adina: Yeah, I'll take a look at it ... I was in the middle
John: Thanks for the catch and the pr!
Adina: Yeah, I'll take a look at it ... I was in the middle of updating the
site for the release and to fix some issues I was having with jekyll. I'll
pick that up again this weekend.
--Aaron
On Fri, Dec 16, 2016 at 8:29 AM Adina Crainiceanu wrote:
> Hi,
Hi, I'm going on vacation today and I did not have time to merge this. If
someone wants to merge it, please do so, otherwise I'll merge it when I
return in Jan.
Happy Holidays to everyone!
Adina
On Thu, Dec 15, 2016 at 2:39 PM, Josh Elser wrote:
One little trick, if you name your pull request s
One little trick, if you name your pull request starting with the JIRA
identifier, "RYA-228", the PR will get automatically linked on the JIRA
issue :)
The change LGTM
John Smith wrote:
Jira issue created
https://issues.apache.org/jira/browse/RYA-228
Pull request
https://github.com/apache/in
Jira issue created
https://issues.apache.org/jira/browse/RYA-228
Pull request
https://github.com/apache/incubator-rya-site/pull/1
Does this look proper?
-- Forwarded message --
From: Puja Valiyil
Date: Wed, Dec 14, 2016 at 11:41 AM
Subject: Re: Do i need a jira ticket for change
