Skip to content

To Fork, or not to Fork

Jonathan Marler edited this page Dec 21, 2018 · 5 revisions

Why Fork?

Walter and Andrei are bad managers.

  • disengaged (they are very busy)
  • poor delegation
  • bad communication
  • very unorganized
  • unclear direction

What goes into the fork?

Initially the fork will be in a "transitionary period" where changes will be more strict. Use the following guidelines for this period:

Can be merged anytime

  • anything that goes into DMD
  • bug fixes
  • test improvements
  • build improvments
  • user experience improvement (i.e. error messages)

Can be merged sometimes

  • new features? maybe. for now any new features must be a superset of what dmd supports. These will have to be evaluated on a case-by-case basis.
  • compiler improvements to a point (want to still be able to merge changes from dmd). These will also have to be evaluated on a case-by-case basis.

Should not be merged

  • deprecations
  • breaking changes

Note that new features/breaking changes can be added if they are put behind feature options (see https://github.com/dragon-lang/dc/issues/61 for more detail)