Re: Zephyr issue tracking system moved to Github

Paul Sokolovsky


On Mon, 25 Sep 2017 11:57:35 +0300
Jukka Rissanen <> wrote:

Hi Anas,

This is not very user friendly atm. For example it is impossible to
find all networking related PR as if I select "area: Networking" I get
only some of the network related PR.

I suggest following change:

* There are too many networking labels, one "area: Networking" is
This RFC from Jukka never got a response, but it seems that everyone
implicitly agreed and followed it, for example:

"area: Networking Clients" has 0 labeled issues
"area: Net Protocols" had 2 issues (closed) over all this time

I seem to be able to edit labels, so unless someone responds to stop
me, I'm going to remove labels above, and leave just "area:
Networking" (183 total issues so far).


On Sat, 2017-09-23 at 22:13 +0000, Nashif, Anas wrote:
As announced earlier this week, we now have migrated all JIRA issues
to github issues:

under GH issues we have kept the components and consolidated some of
them to a more generic label. All components now start with: “area:

Here is how issues types were migrated:
- Bugs = Bugs
- Stories = Enhancements
- Epics = Features/ Feature Requests.

We did keep the links to what used to be stories in epic type
entries and used the format available in Github to link those in.
Assignees that are active in both Jira and Github were set

We will need to have a mega scrub of the issues in Github and
cleanup some outdated items, but I think we do have a good start
Jira ZEP project is now read-only with a link to the corresponding
GH issues entry. GH issues also have a reference to the original ZEP

Please take a look and let us know if you find any problems.

Any new issues should be filed in Github now, Jira will not accept
any new entries.

Zephyr-devel mailing list
Zephyr-devel mailing list

Best Regards,
Paul | Open source software for ARM SoCs
Follow Linaro:!/linaroorg -

Join to automatically receive all group messages.