-
Notifications
You must be signed in to change notification settings - Fork 224
Community CCB Agenda: July 01 2020
Combines 7 PRs!
- https://github.com/nasa/cFS/pull/108
- https://github.com/nasa/cFE/pull/765
- https://github.com/nasa/osal/pull/529
- https://github.com/nasa/PSP/pull/176
- https://github.com/nasa/elf2cfetbl/pull/47
- https://github.com/nasa/cFS-GroundSystem/pull/109
https://github.com/nasa/osal/pull/528
https://github.com/nasa/cFE/pull/763
https://github.com/nasa/osal/pull/527
https://github.com/nasa/cFS-GroundSystem/pull/108
https://github.com/nasa/cFE/pull/764
https://github.com/nasa/to_lab/pull/48
The constellation names will be used going forward to indicate compatible bundle elements.
Releases, prereleases, and release candidates.
- We should provide “extreme clarity” to everyone using cFS
- Multiple questions about compatibility
- SemVer helps to accurately communicate API Changes apps use BOTH cFE and osal APIs
- Accurately answers the question "which version are you using"
- Build-based "version" reporting helps supporting bugs and troubleshooting during development.
- Use tags so testers don’t have to worry about a “moving’ target
We are exploring CalVer to separate the version number for cFE from cFS. The individual repositories will maintain their versions. Every submodule will have a constellation prefix before their version number.
- Use constellation name plus build number for development versions and keep SemVer for tags and releases.
- STOP increaseing the PATCH number for development updates.
- Be explicit in version.h showing both the build string and version number INDICATE that it only refers to the last release.
As stated last week, we will stop increasing the PATCH number each week and instead rely on a new "build number" that will be added to each repository's version.h. This number will be reported in the executable as AppName Development Build CONSTELLATION-NUMBER.
We're still working out the details but the current idea is that this number will be assigned during the merge process.
- Name tags as 6.8.FIX-rcNUMBER (relase candidate)
- Use the prerelease GitHub marker
- All 6.8 developments get added onto the 6.8.x branch as long as they pass the bundle CI
- Create 6.8.x branch on 7/7/2020 (assuming clean CI) and tag with 6.8.0-rc1, use github’s prerelase feature.
GitHub recently shone a spotlight on this though it has been discussed for a while. This shows solidarity with our Black, Indigenous, and People of Color (BIOPOC) developers, users, and community members. This will not solve racism. It is however, important to consider the unconscious and conscious effects that our technological nomenclature can have. I hope this change will drive conversation and I encourage everyone to reach out to me (@astrogeco), your management team, or your diversity and inclusion contacts to learn more about the different ways we can make tech more approachable for everyone. This will make some of us uncomfortable and that's ok.
[P] = Present today
- Jacob Hageman (cFS Framework Lead)
- Jonathan Wilmot (cFS Program Manager)
- Alan Cudmore (cFS Architect)
- Gerardo Cruz-Ortiz (cFS Management)
- Dan Knutsen (cFS Developer)
- Jay Czarnecki (Software Process Imp
- Beth Timmons (GSFC Apps)
- Dwaine Molock (Project Developer)
- Anhelina Yurkova (cFS Test Automation)
- Leor Bleier (cFS Developer)
- Olanrewaju Amoo
- Jandlyn Bentley
- Yasir Khan
- Eric Pollack
- Jandlyn Bentley
- Steve Duran (PSP, OSAL Developer)
- Ron Maglothin (Lunar CATALYST Developer)
- Allen Brown (AES Developer)
- Thomas Brain (AES Integration)
- Tam Ngo AES Lead
- Carrejo, Daniel Systems
- Schlesinger, Adam Avionics and Software
- Thad Flemming
- Chris Knight (SBN Developer & Research)
- Joseph (Pat) Castle
- Michael Scott
- Craig Pires
- Chris Thames (Lead/FSW Management)
- Noah Ryan (Software Developer)
- Deanna Whitehead
- Stefanie Justice
- Lisa Vanderaar (Software lead)
- Joe Hickey (cFS Developer)
- Matt Grubb (SmallSat baseline, build testing)
- Chris Monaco
- Dave McComas (GSFC)