search

joyfullservice / msaccess-vcs-addin

Synchronize your Access Forms, Macros, Modules, Queries, Reports, and more with a version control system.
Other
203 stars 40 forks source link

Release 3.4.0 Steps #234

Closed hecon5 closed 3 years ago

hecon5 commented 3 years ago

Release 3.4.0 issue discussion, see my thoughts below; written in semi-template fashion to be able to reuse for future releases.

Significant Changes / Bug Fixes

Issues we need to close prior to release:

These issues should be closed prior to the release (eg, bugs stem from other issue fixes and can be fixed, features that need to be repaired, or cleanup needed).

Cleanup needed prior to release:

Code tidying, cruft removal, etc. that needs to ensure the release code is 'tidy'.

Bug Issues not in release scope:

Issues that are known, but are too complex to fix under this release, or have been endemic to Addin and are not degradation of feature sets, or are currently out of scope / planned for the future. Issue|Description|Disposition & Reason for exclusion

Feature Issues not in release scope:

Any other release caveats:

Items we need to consider prior to release.

[Edit]: below is no longer correct, it's been addressed, can still import from prior db versions.

joyfullservice commented 3 years ago

Thanks for putting this together! I wonder if milestones might be a good fit for this... We could then assign the relevant issues to the milestone, and include some of the notes in the milestone description.

hecon5 commented 3 years ago

We use Jira for our feature/issue tracking, and use their release version to track this, and it makes it a breeze to track what's happening version to version. It's a combination of Issue Tracking, GitHub Projects, milestones (if I understand correctly, GitHub Milestones ~= Releases in Jira).

The thing I really like is that it automatically moves tickets along, so you can see what's integrated to stable, still in beta ('dev' in this case), being worked on, troubleshooting stages, etc. And as an issue gets moved along, it closes/changes state. Also makes creating a release log as easy as remembering to tag your commits; click "See Issue notes" and it's done.

Anyway, that's a long-winded way to say "I like it, and I'm all for automating mundane tasks out of needing to be done".

hecon5 commented 3 years ago

In the https://github.com/msaccess-vcs-integration/msaccess-devops/projects/1 I set up a project / milestone for Kanban, which makes issue tracking easier than using GitHub's standard one (especially for sorting into future/tbd/working/bug to be fixed now/ etc buckets), take a peek

A9G-Data-Droid commented 3 years ago

Generally, the major version number is used to indicate breaking change. So we would roll to version 4.0 so you can explain that this version is not compatible with previous versions.

hecon5 commented 3 years ago

Update: no longer a breaking change, updated above.

hecon5 commented 3 years ago

Ready for launch?

joyfullservice commented 3 years ago

I think we are ready for launch! 🚀 I will see if I can get the release notes put together and push this out today!

hecon5 commented 3 years ago

Closing, released!

Indigo744 commented 3 years ago

I just want to take the time to say thank you 😸 Really thank you all for the tremendous amount of work you are all doing on this!