Is the plan to develop in the open from now on, or to drop releases developed in private in large flattened commits like this?
Is the plan to develop in the open from now on, or to drop releases developed in private in large flattened commits like this?
I literally chuckled when I read your comment. It sounds reasonable to flatten commits before a release, as I, and others, who are hacking on code litter their history with "fix this" / "fix that" / "asjhdasjd" / "f**".
Open source model doesn't mean version control transparency. Open source model could also be development done in a private fork, and release commits dumped into a public repository.
In my experience this is how open source projects tend to thrive in the last 15 years or so. Projects that are open source but don't accept contributions and just dump a zip on a website somewhere once a year are a very different thing and lose some of the benefits.