Closed james2doyle closed 8 years ago
Aside from the question how to proceed with 2.* in general, can you point to what you mean specifically?
It seems like I mixed up the release for 2.x and this release draft
maybe a side-effect or reason for our problem with composer (#294) ?
Ah. That was just the template for the "next" release as in "nobody knows if it will be 1.7.2 or 1.8.0".
I have the habit of setting up a new empty "next" release note right after a release is done. Then every time an issue is resolved or a PR is merged you can immediately write down a changlog line or other important info as long as the full context is in your head anyway.
In my experience it's much less time consuming and generates better quality content than writing it up later.
Looks like some of the 2.* stuff contains some of the information that was merge in 1.7.0