You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4j-dev@logging.apache.org by Mikael Ståldal <mi...@magine.com> on 2016/08/27 12:30:40 UTC
GitHub pull requests
Does anyone keep track of incoming pull requests on GitHub? It seems like
we get a few with no corresponding JIRA ticket. Should we ask them to open
a JIRA ticket?
Re: GitHub pull requests
Posted by Mikael Ståldal <mi...@magine.com>.
Someone should have a look at this Pull Request:
https://github.com/apache/logging-log4j2/pull/41
I am not sure if it makes sense or not.
On Tue, Aug 30, 2016 at 7:10 PM, Mikael Ståldal <mi...@magine.com>
wrote:
> Done.
>
> On Sun, Aug 28, 2016 at 12:20 PM, Remko Popma <re...@gmail.com>
> wrote:
>
>> +1 Good idea!
>>
>> On Sun, Aug 28, 2016 at 7:12 PM, Mikael Ståldal <
>> mikael.staldal@magine.com> wrote:
>>
>>> I think that some people find the project on GitHub, and they might not
>>> be aware about our JIRA. Should we mention this in the README.md that is
>>> visible on GitHub?
>>>
>>> On Aug 27, 2016 2:30 PM, "Mikael Ståldal" <mi...@magine.com>
>>> wrote:
>>>
>>>> Does anyone keep track of incoming pull requests on GitHub? It seems
>>>> like we get a few with no corresponding JIRA ticket. Should we ask them to
>>>> open a JIRA ticket?
>>>>
>>>
>>
>
>
> --
> [image: MagineTV]
>
> *Mikael Ståldal*
> Senior software developer
>
> *Magine TV*
> mikael.staldal@magine.com
> Grev Turegatan 3 | 114 46 Stockholm, Sweden | www.magine.com
>
> Privileged and/or Confidential Information may be contained in this
> message. If you are not the addressee indicated in this message
> (or responsible for delivery of the message to such a person), you may not
> copy or deliver this message to anyone. In such case,
> you should destroy this message and kindly notify the sender by reply
> email.
>
--
[image: MagineTV]
*Mikael Ståldal*
Senior software developer
*Magine TV*
mikael.staldal@magine.com
Grev Turegatan 3 | 114 46 Stockholm, Sweden | www.magine.com
Privileged and/or Confidential Information may be contained in this
message. If you are not the addressee indicated in this message
(or responsible for delivery of the message to such a person), you may not
copy or deliver this message to anyone. In such case,
you should destroy this message and kindly notify the sender by reply
email.
Re: GitHub pull requests
Posted by Mikael Ståldal <mi...@magine.com>.
Done.
On Sun, Aug 28, 2016 at 12:20 PM, Remko Popma <re...@gmail.com> wrote:
> +1 Good idea!
>
> On Sun, Aug 28, 2016 at 7:12 PM, Mikael Ståldal <mikael.staldal@magine.com
> > wrote:
>
>> I think that some people find the project on GitHub, and they might not
>> be aware about our JIRA. Should we mention this in the README.md that is
>> visible on GitHub?
>>
>> On Aug 27, 2016 2:30 PM, "Mikael Ståldal" <mi...@magine.com>
>> wrote:
>>
>>> Does anyone keep track of incoming pull requests on GitHub? It seems
>>> like we get a few with no corresponding JIRA ticket. Should we ask them to
>>> open a JIRA ticket?
>>>
>>
>
--
[image: MagineTV]
*Mikael Ståldal*
Senior software developer
*Magine TV*
mikael.staldal@magine.com
Grev Turegatan 3 | 114 46 Stockholm, Sweden | www.magine.com
Privileged and/or Confidential Information may be contained in this
message. If you are not the addressee indicated in this message
(or responsible for delivery of the message to such a person), you may not
copy or deliver this message to anyone. In such case,
you should destroy this message and kindly notify the sender by reply
email.
Re: GitHub pull requests
Posted by Remko Popma <re...@gmail.com>.
+1 Good idea!
On Sun, Aug 28, 2016 at 7:12 PM, Mikael Ståldal <mi...@magine.com>
wrote:
> I think that some people find the project on GitHub, and they might not be
> aware about our JIRA. Should we mention this in the README.md that is
> visible on GitHub?
>
> On Aug 27, 2016 2:30 PM, "Mikael Ståldal" <mi...@magine.com>
> wrote:
>
>> Does anyone keep track of incoming pull requests on GitHub? It seems like
>> we get a few with no corresponding JIRA ticket. Should we ask them to open
>> a JIRA ticket?
>>
>
Re: GitHub pull requests
Posted by Mikael Ståldal <mi...@magine.com>.
I think that some people find the project on GitHub, and they might not be
aware about our JIRA. Should we mention this in the README.md that is
visible on GitHub?
On Aug 27, 2016 2:30 PM, "Mikael Ståldal" <mi...@magine.com> wrote:
> Does anyone keep track of incoming pull requests on GitHub? It seems like
> we get a few with no corresponding JIRA ticket. Should we ask them to open
> a JIRA ticket?
>
Re: GitHub pull requests
Posted by Matt Sicker <bo...@gmail.com>.
If you go here:
https://issues.apache.org/jira/secure/ManageFilters.jspa
You can see there's a "Shared With" column. In theory, we can make a filter
public, but I can't find how.
On 27 August 2016 at 11:26, Gary Gregory <ga...@gmail.com> wrote:
> Jira has a SQL like query language... and you can save queries. But that
> might be per user.
>
> Gary
>
> On Aug 27, 2016 8:39 AM, "Ralph Goers" <ra...@dslextreme.com> wrote:
>
>> Yes, every patch needs a Jira issue.
>>
>> To be honest, I’d really like a tool that could tell us all the Jira
>> issues that have patches and all the outstanding pull requests. I am sure
>> there are commands or queries that could do both of these things but I
>> don’t remember exactly how to do them. It would be nice just to have a
>> button to push somewhere.
>>
>> Ralph
>>
>> On Aug 27, 2016, at 5:30 AM, Mikael Ståldal <mi...@magine.com>
>> wrote:
>>
>> Does anyone keep track of incoming pull requests on GitHub? It seems like
>> we get a few with no corresponding JIRA ticket. Should we ask them to open
>> a JIRA ticket?
>>
>>
>>
--
Matt Sicker <bo...@gmail.com>
Re: GitHub pull requests
Posted by Gary Gregory <ga...@gmail.com>.
Jira has a SQL like query language... and you can save queries. But that
might be per user.
Gary
On Aug 27, 2016 8:39 AM, "Ralph Goers" <ra...@dslextreme.com> wrote:
> Yes, every patch needs a Jira issue.
>
> To be honest, I’d really like a tool that could tell us all the Jira
> issues that have patches and all the outstanding pull requests. I am sure
> there are commands or queries that could do both of these things but I
> don’t remember exactly how to do them. It would be nice just to have a
> button to push somewhere.
>
> Ralph
>
> On Aug 27, 2016, at 5:30 AM, Mikael Ståldal <mi...@magine.com>
> wrote:
>
> Does anyone keep track of incoming pull requests on GitHub? It seems like
> we get a few with no corresponding JIRA ticket. Should we ask them to open
> a JIRA ticket?
>
>
>
Re: GitHub pull requests
Posted by Ralph Goers <ra...@dslextreme.com>.
Yes, every patch needs a Jira issue.
To be honest, I’d really like a tool that could tell us all the Jira issues that have patches and all the outstanding pull requests. I am sure there are commands or queries that could do both of these things but I don’t remember exactly how to do them. It would be nice just to have a button to push somewhere.
Ralph
> On Aug 27, 2016, at 5:30 AM, Mikael Ståldal <mi...@magine.com> wrote:
>
> Does anyone keep track of incoming pull requests on GitHub? It seems like we get a few with no corresponding JIRA ticket. Should we ask them to open a JIRA ticket?
>