Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Any good documentation that talks about how big open source software manage code changes, releases cadences, given contributors from across the world.


I'm fairly sure this differs for different project/organization, not sure there is a rule, and not sure there are really any considerations that are specific to open source, good practices are good practices regardless.

That being said, I rate Canonical's practices as rather poor.


Taking an example, how are Linux Kernel releases are planned and managed




Consider applying for YC's Winter 2026 batch! Applications are open till Nov 10

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: