On Mon, Mar 5, 2018 at 6:07 PM, Keith Turner wrote:
> On Thu, Feb 15, 2018 at 12:52 PM, Josh Elser wrote:
>> -0 as an initial reaction because I'm still not convinced that GH issues
>> provides any additional features or better experience than JIRA does, and
>> this change would only serve to fra
>
> 4. What is the migration plan for existing issues? Will we have split
> issue
>tracker for years?
>
> The proposal documents migrating existing JIRA issues as they are worked.
> This means that existing JIRA issues that are never worked will never
> migrate. After all branches are re
On Wed, Mar 7, 2018 at 11:17 AM, Mike Walch wrote:
>>
>> 4. What is the migration plan for existing issues? Will we have split
>> issue
>>tracker for years?
>>
>> The proposal documents migrating existing JIRA issues as they are worked.
>> This means that existing JIRA issues that are nev
Sorry for the top-post.
I really appreciate the numbered list below, Keith. Specifically the
answers to #1 and #4 make me very happy.
I think #5 needs some a little more concrete (IMO, you should just
decide what it should be).
#6 +1 to a message to private, this is how Apache general reque
On Wed, Mar 7, 2018 at 11:50 AM, Josh Elser wrote:
> Sorry for the top-post.
>
> I really appreciate the numbered list below, Keith. Specifically the answers
> to #1 and #4 make me very happy.
>
> I think #5 needs some a little more concrete (IMO, you should just decide
> what it should be).
My w
On Wed, Mar 7, 2018 at 11:50 AM Josh Elser wrote:
> Sorry for the top-post.
>
> I really appreciate the numbered list below, Keith. Specifically the
> answers to #1 and #4 make me very happy.
>
> I think #5 needs some a little more concrete (IMO, you should just
> decide what it should be).
>
> #
