I think it's a good idea to use the labels for triage and priority. It will
make the PR and issue view much simpler on Github.
If it's not used on Github, does it mean that all PR/issue on Github must
have a JIRA and the triage/sorting is only done there?
Marc-Aurèle
On Wed, Oct 26, 2016 at 7:18
All,
Now that we're getting some testing momentum going, I was thinking that we need
a way to categorise and prioritise the PR queue.
There are a limited number of labels available for use to apply to the PRs
within Github as it is, but we could go through and highlight bug fixes and
rity of any other PRs.
> On Mar 17, 2016 5:06 PM, "ilya" <ilya.mailing.li...@gmail.com> wrote:
>
>> Hi Folks,
>>
>> What can we do about PR backlog in GitHub? As we all know, it will be
>> very difficult to merge the changes - as things will get out of sync.
>>
;
Sent: Thursday, March 17, 2016 4:06 PM
To: dev@cloudstack.apache.org
Subject: [IMPORTANT] Huge Github PR Backlog
Hi Folks,
What can we do about PR backlog in GitHub? As we all know, it will be
very difficult to merge the changes - as things will get out of sync.
Feedback is welcome,
Thanks,
ilya
>
> >
> >
> >
> >From: ilya <ilya.mailing.li...@gmail.com>
> >Sent: Thursday, March 17, 2016 4:06 PM
> >To: dev@cloudstack.apache.org
> >Subject: [IMPORTANT] Huge Github PR Backlog
> >
>
t;
>Just my 2 cents.
>
>- Si
>
>
>
>
>
>From: ilya <ilya.mailing.li...@gmail.com>
>Sent: Thursday, March 17, 2016 4:06 PM
>To: dev@cloudstack.apache.org
>Subject: [IMPORTANT] Huge Github PR Backlog
>
>Hi Folks,
>
>Wha
Hi Folks,
What can we do about PR backlog in GitHub? As we all know, it will be
very difficult to merge the changes - as things will get out of sync.
Feedback is welcome,
Thanks,
ilya
...@gmail.com> wrote:
> Hi Folks,
>
> What can we do about PR backlog in GitHub? As we all know, it will be
> very difficult to merge the changes - as things will get out of sync.
>
> Feedback is welcome,
>
> Thanks,
> ilya
>
