GitLab | Workflow for contrib projects (#99)

[Amar Takhar (@amar)]

Amar Takhar commented on a discussion: https://gitlab.rtems.org/administration/gitlab/-/issues/99#note_124711


We did talk about that and the mirror will never be a fork we already deal with this now and it would just remain a patch sitting on an issue somewhere?

The issue is if we start merging into a hard fork it's very, very easy for changes to be forgotten then things will bitrot.  Unfortunately if we do have a longterm change that we want and that is not accepted upstream we'll have to find a different solution it's not tenable to maintain patches forever.

The proposed model keeps things on the surface constantly so we can't forget about not upstreaming changes they'll always just sit as patches applied by the RSB and eventually we'll have to deal with it by upstreaming it or finding a way to not require the patch those are the only three options available to us.

-- 
View it on GitLab: https://gitlab.rtems.org/administration/gitlab/-/issues/99#note_124711
You're receiving this email because of your account on gitlab.rtems.org.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/bugs/attachments/20250616/613ef10a/attachment.htm>