Version 6.0.0 release #721
Replies: 11 comments 12 replies
Sounds like a good workflow to me :) |
|
This project has just used Github release notes up till now, is there a reason we cannot simply document the changes there this time too? Why switch to a CHANGELOG in the repo after all this time? |
|
Did my best to review the three PRs mentioned here. |
|
Does this release actually introduce draft-06 support? I didn't think so but I saw a reference to it in another thread. |
|
I took the liberty to start sharing some data points in an effort to complete the changelog . Perhaps I'm doing duplicate work and @dafeder has already passed this step, but that's my risk. It seems like from below lists we have all the info needed to make a decent changelog and filter out duplicates from the Common baseBased on running Commits on
|
|
From the commits on master since the common base I've derived the below changelog. The only think left to do is remove the backports from version Changelog[6.0.0] - 2024-XX-XXAdded
Changed
Deprecated
Removed
Fixed
|
|
Removing the backports we are left with: Changelog[6.0.0] - 2024-XX-XXAdded
Changed
Deprecated
Removed
Fixed
|
|
Beta release is out 🥳 Next step is doing some smoke testing / create draft PR for mayor application/libraries using this library. |
|
@DannyvdSluijs thanks for doing this, I apologize I was not able to get far with this, I got very sidetracked with my main project and some other things and was honestly a little overwhelmed since the list was so long and I was so unfamiliar with most of the issues. I will do some testing with the beta release on DKAN and report any issues I see. |
|
Initial smoke testing has gone somewhat okay. During the PR for Composer we learned that In general, I would opt to move forward with the |
|
Version |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
I believe this project to be very close to the version 6.0.0 release. A couple of things could/should be done before we can make it so. Let's use this place to discuss and see how to move forward.
Some things that are at the top of my head are:
CHANGELOG.mdas outlined per https://keepachangelog.com/en/1.1.0/. Perhaps the compare from GitHub betweenv5.2.13andmastercan provide some insightsPHPInsights: PHPInsight isn't depending onjson-schemabut was having a leftoverrequire, see #6886.0.0-betawhich can help with the suggested smoke testingBased on the permissions granted to me by @Seldaek I should be able to manage the release process. I'm mostly curious about the thoughts and opinions of others. So also pinging @dafeder and @paul-m.
All reactions