Update Tyr Upstream Development Process#55
Conversation
deborahbrouwer
force-pushed
the
tyr-update
branch
from
c0243f2 to
0f72876
Compare
|
It sounded to me like @dwlsalmeida was saying that MRs to the prototype would now have a specific purpose (i.e. doing testing that requires a working driver). If that is the case, i.e. if downstream/prototype development is not expected to be common anymore, then perhaps the page should be reorganized a bit? But maybe I misinterpreted what he meant. Happy new year! |
| To work on any given task, assign it to yourself. For patches targeting the downstream | ||
| staging branch, open a merge request against `tyr-dev`. |
There was a problem hiding this comment.
I would suggest mentioning the upstream route too or removing both, instead of mentioning only the downstream case (the text before the change has both too).
(But please see my comment above)
ojeda
force-pushed
the
main
branch
6 times, most recently
from
945c60c to
cb1de5a
Compare
|
@ojeda, now that I've become more familiar with Tyr, I do think a general reorganization would be helpful for this page. I'll propose something more succinct and less prescriptive shortly. |
|
Sounds good, thanks for taking a look again! (I noticed the PR while doing something else) |
Currently the upstream development process for Tyr suggests that a developer could open a merge request for review and discussion in the panfrost-linux repository on Freedesktop GitLab. While merge requests can still be a useful collaboration tool, other DRM developers might not be reading those merge requests, so to be absolutely clear, just direct new upstream contributions to the mailing lists. Signed-off-by: Deborah Brouwer <deborah.brouwer@collabora.com>
deborahbrouwer
force-pushed
the
tyr-update
branch
from
0f72876 to
48f5d03
Compare
2 participants
This MR makes it clear that upstream contributions can go right to mailing lists.
As suggested by @dakr and @dwlsalmeida in #52
@ojeda could you please review?