I was going to only apply it to the os repo so we have one place to
triage/manage and people might not know where to file an issue or I
might span both. We can use labels to further filter, this is how I
usually see it done for projects with multiple repos.
We can always enable the apps one
t;> On Mon, Dec 30, 2019, 11:02 PM 张铎(Duo Zhang)
>>>>>> wrote:
>>>>>>
>>>>>>> For me I suggest we start with GitHub issues.
>>>>>>>
>>>>>>> For problem #1, the cross repo PRs, I think it is
epo PRs, I think it is fine to have only
>>>>>> one issue in the main repo? We can reference multiple PRs in an issue and
>>>>>> the PRs could come from other repos.
>>>>>>
>>>>>> And for problem #2, once the user sends the patch to this mailing
>>>>&g
uty to open an issue for this, and also open a
>>>>> PR with this patch to let others review and get the patch in finally.
>>>>>
>>>>> I think for most projects which use JIRA, is just because that GitHub
>>>>> was not available when the proj
t others review and get the patch in finally.
>>>>
>>>> I think for most projects which use JIRA, is just because that GitHub
>>>> was not available when the project was set up. And then the work flow, and
>>>> release processing are already bound with JI
ut I think for a new project, just make use of GitHub is
>>> fine.
>>>
>>> Of course I'm also fine with using JIRA, no problem. Just a suggestion.
>>>
>>> Thanks.
>>>
>>> David Sidrane 于2019年12月31日周二 上午1:47写道：
>>>
>>>
g JIRA, no problem. Just a suggestion.
>>
>> Thanks.
>>
>> David Sidrane 于2019年12月31日周二 上午1:47写道：
>>
>>> Hi Brenan,
>>>
>>>
>>>
>>> See Below.
>>>
>>>
>>>
>>> -Original Message-
>>&g
On Thu, Jan 9, 2020 at 6:55 PM Gregory Nutt wrote:
> Another thing, most issues are reported by email. How would that fit in?
>
One of two ways.
Either we'd ask the reporter to file an issue.
Or we would file the issue ourselves.
Either way, triaging of issues would need to be an ongoing eff
n [mailto:bash...@brennanashton.com
<mailto:bash...@brennanashton.com>]
Sent: Monday, December 30, 2019 8:52 AM
To: dev@nuttx.apache.org <mailto:dev@nuttx.apache.org>
Subject: Re: Issue Reporting
Can people who are advocating for GitHub address the two main
8:52 AM
To: dev@nuttx.apache.org <mailto:dev@nuttx.apache.org>
Subject: Re: Issue Reporting
Can people who are advocating for GitHub address the two main
points that I
had made. The second one I really don't see a workaround for.
To be clear
renan,
>>
>>
>>
>> See Below.
>>
>>
>>
>> -Original Message-
>> From: Brennan Ashton [mailto:bash...@brennanashton.com]
>> Sent: Monday, December 30, 2019 8:52 AM
>> To: dev@nuttx.apache.org
>> Subject: Re: Issue Reportin
>
> See Below.
>
>
>
> -Original Message-
> From: Brennan Ashton [mailto:bash...@brennanashton.com]
> Sent: Monday, December 30, 2019 8:52 AM
> To: dev@nuttx.apache.org
> Subject: Re: Issue Reporting
>
>
>
> Can people who are advocating for GitHub add
Hi Brenan,
See Below.
-Original Message-
From: Brennan Ashton [mailto:bash...@brennanashton.com]
Sent: Monday, December 30, 2019 8:52 AM
To: dev@nuttx.apache.org
Subject: Re: Issue Reporting
Can people who are advocating for GitHub address the two main points that I
had made. The
+1 for github
There has been no formal [VOTE] started. Any formal vote must be
preceded by a [DISCUSS] so that we can all understand the issues and we
can all be qualified to vote.
It is probably too early to start a discussion or vote since we have not
eventthe vaguest plan in place fo
Can people who are advocating for GitHub address the two main points that I
had made. The second one I really don't see a workaround for. To be clear
if we can get around both of these I'm happy to be on the GitHub train.
1) Multiple repos. We might have an issue or feature the spans the os,
ap
+1 for github
On Mon, Dec 30, 2019, 18:32 Gregory Nutt wrote:
> > I'm a little torn on this one, but I'd say Github wins for me.
> Are they mutually exclusive?
>
I'm a little torn on this one, but I'd say Github wins for me.
Are they mutually exclusive?
My experience with Jira is that it is powerful if you know how to use it,
but that it can be really clumsy and difficult to learn. There's also a lot
of pain with certain actions, like switching issue types in bulk and things
like that.
Github on the other hand is much more straightforward and sim
Lots of Jira tutorials. Not knowing how to use it does not not sound
like a strong argument against it:
Quick Google:
https://www.guru99.com/jira-tutorial-a-complete-guide-for-beginners.html
https://www.atlassian.com/agile/tutorials
https://www.atlassian.com/software/jira/guides/getting-star
Jerpelea [mailto:jerpe...@gmail.com]
Sent: Monday, December 30, 2019 1:23 AM
To: dev@nuttx.apache.org
Subject: Re: Issue Reporting
for another bug tracker we use github and all issued are created on a
template.
This template can start with the following title "git name - board /
comp
for another bug tracker we use github and all issued are created on a
template.
This template can start with the following title "git name - board /
component - version - issue".
Such layout eases the sorting and people can easy spot if there is
something similar to theyr issue.
On Mon, Dec 3
I like this. I prefer that we use Apache's Jira for several reasons,
especially in light of the integration that Brennan describes.
If we do go with Jira, we should transfer all of the Bitbucket nuttx/
and apps/ issues to Jira along with the content of the NuttX TODO list.
I like this. I prefer that we use Apache's Jira for several reasons,
especially in light of the integration that Brennan describes.
I think we should give it a try. I don't know enough to have a strong
opinion.
Jira also integrates with an Agile project management process. Is that
someth
On Sun, Dec 29, 2019 at 7:46 PM Brennan Ashton
wrote:
> Normally I am a fan of keeping things simple and using the simple github
> issue tracker, but we have a few issues that I think make that less
> practical.
>
> 1) Multiple repos. We might have an issue or feature the spans the os,
> app, an
Normally I am a fan of keeping things simple and using the simple github
issue tracker, but we have a few issues that I think make that less
practical.
1) Multiple repos. We might have an issue or feature the spans the os,
app, and website repos now we need to file tickets in each or something
eq
25 matches
Mail list logo
