Documentation
Development process
- Cross-Toolchain upgrade toolchain.git
- Review TODOs and Flispray bugs, from CRUX and CRUX-ARM
- Sync versions with upstream
- Fill TODO with problems/fixes
- First update to Ohloh project with newer repos and branches
- Initrd initrd.git
- Initrd creation is used to check if Cross-toolchain is working right, avoiding the step of cross building all core ports
- Review TODOs and Flispray bugs from CRUX-ARM
- Update if needed (check Changelog)
- Create and test initrd with current toolchain (used to build device kernel target and bootloader files with Cross-Toolchain too)
- Update to Ohloh project with newer repos and branches
- Pkgutils-cross pkgutils-cross.git
- Review TODOs and Flispray bug, from CRUX and CRUX-ARM
- Sync versions with upstream
- Fill TODO with problems/fixes
- Update to Ohloh project with newer repos and branches
- crossrootfs crossrootfs.git
- Review TODOs and Flispray bug, from CRUX and CRUX-ARM
- Sync versions with upstream
- Fill TODO with problems/fixes
- "First stage" -> create cross-ports from crossrootfs.git (first pass as CRUX iso.git)
- Update to Ohloh project with newer repos and branches
- Generic release creation
- Once core-cross ports (built from crossrootfs.git) are ready, we can use devtools to create first crossrootfs-generic RC1 release to deploy it to the powerfull device and build the final generic release
- With core-rootfs deployed to the powerfull device, all core ports will be rebuilt with generic cflags and removing optimizations from ports if they add them (using PORTS/core-arm overlay without updating pkgmk.conf and respect CFLAGS and CRUX core ports from version tag when it was released, with devtools/crossrootfs-extra script help)
- "Second stage" -> Build the final generic release in a device to avoid cross references (second pass as chroot in CRUX iso.git)
- Release test process
- Deploy to all supported official devices for testing
- Create all needed sections in Flispray
- Review Ohloh project to verify that all newer info is added.
- Announce the new release in ML
- Optimized releases and contrib process open
- Open the contribute window for other users who wants to add another devices support. Check how to do it:
- Rebuild native ports with optimized flags for all official devices (we are using -march=native)