search

ZeligsoftDev / CX4CBDDS

CX4CBDDS component modeling and generation tool
Apache License 2.0
8 stars 5 forks source link

Tag streams/v2.1.x-maintenance for Zeligsoft CX 2.1.1 release and roll branch to 2.1.2 #419

Closed J17359 closed 2 years ago

J17359 commented 2 years ago

Issue and tracking information

Developer's time Estimated effort to fix (hours):

Developer's Actual time spent on fix (hours)

Issue reporter to provide a detailed description of the issue in the space below

Our program would like to release with your latest hash from the streams/v2.1.x-maintenance branch. Could you please tag that hash for an officially supported release (2.1.1) and then roll the pom.xml's to 2.1.2 for our next release to target on that 2.1.X baseline?

elder4p commented 2 years ago
J17359 commented 2 years ago

Thanks for the super quick turnaround @elder4p !

J17359 commented 2 years ago

@elder4p were the two issues under "What's Changed" on that release page just the big ticket items? The "Full Changelog" shows more than those two issues in the commit history. Should all those be listed under "What's Changed"?

elder4p commented 2 years ago

@elder4p were the two issues under "What's Changed" on that release page just the big ticket items? The "Full Changelog" shows more than those two issues in the commit history. Should all those be listed under "What's Changed"?

@J17359 : You're right. Github offered the What's Changed list. I removed one issue from it (bumping the version numbers), but I did not look at the full change log. Clearly, the automated process didn't do what I expected. I'll go through the full change log manually, and pull out the issues that look like they are pertinent.

elder4p commented 2 years ago

@J17359 : Updated the list to link to all tickets resolved in the release. This is still different from the full change log, as it shows all commits, pull request merges, etc. Not quite the same thing.

Let me know if this is OK.

(I still don't know why the 'generated' release notes where so sparse. Lesson learned: don't count on it working.)

J17359 commented 2 years ago

@J17359 : Updated the list to link to all tickets resolved in the release. This is still different from the full change log, as it shows all commits, pull request merges, etc. Not quite the same thing.

Let me know if this is OK.

(I still don't know why the 'generated' release notes where so sparse. Lesson learned: don't count on it working.)

Yeah I think that looks a lot better. I didn't expect the commits, PR merges, etc. to be in the list, only the ticket IDs which it looks like you got now. Thanks @elder4p ! Very weird that the autogenerated version didn't work, I agree.

ysroh commented 2 years ago

Can we close this ticket?

J17359 commented 2 years ago

Can we close this ticket?

I think we're still waiting on the PR to be merged: https://github.com/ZeligsoftDev/CX4CBDDS/pull/420

elder4p commented 2 years ago

Fixed by #420