#25 Remove deprecated files
Closed by bignose. Opened by hberaud.
hberaud/python-daemon refactor-cleanup  into  master

Download 25.patch

Since we have propose to refactor the project
release management by using pbr we now propose to remove
deprecated files used in the past to build and generate releases.

In order merge these pull request before:
1 => https://pagure.io/python-daemon/pull-request/23
2 => https://pagure.io/python-daemon/pull-request/24

Co-authored-by: Hobbestigrou hobbestigrou@erakis.eu

Please be careful to merge these pull requests in order:

  1. 23

  2. 24

  3. 25

  4. 26

Thank you

What does “deprecated” mean, here?

These modules provide the capability to use the Changelog as the canonical location of the current version string.

I don't see what you're proposing that would continue to provide that feature.

We can keep these files if you want.

I removed them due to pbr introduction.
PBR automatize:
- changelog generation
- authors file generation
- version number management

deprecated mean that these files are unnecessary since we introduce pbr.

We can keep these files if you want.

I removed them due to pbr introduction.
PBR automatize:
- changelog generation
- authors file generation
- version number management

deprecated mean that these files are unnecessary since we introduce pbr.

PBR automatize:
- changelog generation

Automates it how? The content of a changelog document is not kept anywhere else.

If you're thinking of the Git commit messages, those are entirely different. Those messages are targeted to people viewing individual commits, like developers working on the project.

A change log document is not mechanically generated from the Git commit messages; it is targeted not to the project developers but to the users. See the https://keepachangelog.com/ site for more explanation.

So I think that removing these modules is not appropriate for this project.

Pull-Request has been closed by bignose

Metadata