LibBSD | dev/mmc/mmcsd: Remove media server requirement for mmcsd (!84)

[Chris Johns (@chris)]

Chris Johns commented on a discussion: https://gitlab.rtems.org/rtems/pkg/rtems-libbsd/-/merge_requests/84#note_129630


Missing changes on `main` need issues to be tracked down.

We need the branches we have and we cannot and should not be developing on FreeBSD `CURRENT`. We need to formalize the process so an updated `README` is a good idea.

1. We need to refer to FreeBSD naming when discussing FreeBSD code. They have `CURRENT` for development, `stable` for work on release branches and `releng` for each release. We should only track `CURRENT` and `releng` branches. This makes the work we do simpler because we only need to deal with `releng` branches when they are created or updated. We will not track and maintain different FreeBSD versions of a release as separate Libbsd branches and packages. For example `6-freebsd-14` tracks the latest FreeBSD 14 release once updated.
2. Our `main` branch tracks FreeBSD `CURRENT`. We require this branch builds with our development release of RTEMS. Target testing is optional.
3. Our development branch is based on the next RTEMS version and the latest FreeBSD `releng` branch, ie the latest FreeBSD version released. At the moment this is `7-freebsd-14`. It would be way to hard developing new code on `CURRENT` as it may not be stable and you would be fighting two unknowns. 
4. Our development branch moves to the next FreeBSD released version when FreeBSD releases it. We can then determine which changes we make to back port to previous FreeBSD releases and also RTEMS releases.

This process is not perfect. There will be difficult pressure points over time. For example a development we undertake uses FreeBSD kernel interfaces that have changed on `CURRENT`. We will have to discuss and deal with those when we encounter them. I faced this with the VFS work.

-- 
View it on GitLab: https://gitlab.rtems.org/rtems/pkg/rtems-libbsd/-/merge_requests/84#note_129630
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/20250827/510ddb6e/attachment.htm>