Improve developer experience of maintaining fork
Description
- How can we improve the developer experience of adding and maintaining the changes we make ontop of the base VSCode?
- How can we improve the developer experience of receiving new updates
Ideas
- Let's introduce a set of
CHANGELOGentries (I'm anticipating separate files) which represent our cohesive set of changes on-top of the- Every one of our commits must have a reference to a
CHANGELOGentry. This way we have a clear idea of what commits belong squashed together.
- Every one of our commits must have a reference to a
- Let's see if we can remove the
VERSIONfile and just use tags. - Let's introduce a script that can be run locally to guide the developer with upgrading the base VSCode version. Maybe we could also have a script to help developers review VSCode version upgrades?
Edited by Paul Slaughter