Skip to content

Packaging: Auto-generate changelog during configure #15528

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Nov 16, 2023

Conversation

umsaleem
Copy link

Motivation and Context

With new releases and version updates, contrib/debian/changelog needs to be updated with a new changelog entry, this adds an extra step for release process.

Description

Auto-generate changelog based off on @VERSION@ during configure, so that it is not needed to be update with new releases / version updates.

How Has This Been Tested?

Created native Debian packages after the update. Confirmed they are generated with same version, as before (2.2.99 for master branch).

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Performance enhancement (non-breaking change which improves efficiency)
  • Code cleanup (non-breaking change which makes code smaller or more readable)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Library ABI change (libzfs, libzfs_core, libnvpair, libuutil and libzfsbootenv)
  • Documentation (a change to man pages or other documentation)

Checklist:

Auto-generate changelog based off on @Version@ during configure,
so that it is not needed to be update with new releases / version
updates.

Signed-off-by: Umer Saleem <[email protected]>
@umsaleem umsaleem mentioned this pull request Nov 15, 2023
13 tasks

* OpenZFS @VERSION@ is tagged.

-- Umer Saleem <[email protected]> Wed, 15 Nov 2023 15:00:00 +0500
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I assume it's ok to leave the date as a static Wed, 15 Nov 2023 15:00:00 +0500 here right?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, I think should be. Ideally this should be the date of the release, but since we are not doing that, and the other option is to insert the current time stamp (at the time configure runs), which is not correct either, I think setting to a prior date should be alright.

@tonyhutter tonyhutter merged commit 5796e3a into openzfs:master Nov 16, 2023
@umsaleem umsaleem deleted the NAS-125230 branch November 16, 2023 17:40
ixhamza pushed a commit to truenas/zfs that referenced this pull request Nov 20, 2023
Auto-generate changelog based off on @Version@ during configure,
so that it is not needed to be update with new releases / version
updates.

Signed-off-by: Umer Saleem <[email protected]>
Reviewed-by: Tony Hutter <[email protected]>
ixhamza added a commit to truenas/zfs that referenced this pull request Nov 20, 2023
lundman pushed a commit to openzfsonwindows/openzfs that referenced this pull request Dec 12, 2023
Auto-generate changelog based off on @Version@ during configure,
so that it is not needed to be update with new releases / version
updates.

Signed-off-by: Umer Saleem <[email protected]>
Reviewed-by: Tony Hutter <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants