Skip to content
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

Changelog missing version dates for legacy reference #56

Open
qriff opened this issue Aug 8, 2018 · 7 comments
Open

Changelog missing version dates for legacy reference #56

qriff opened this issue Aug 8, 2018 · 7 comments

Comments

@qriff
Copy link

qriff commented Aug 8, 2018

Changelog missing version dates for legacy reference

@russhaun
Copy link

russhaun commented Aug 8, 2018

hey whats up just saw your post and decided to look at the changelog file. not sure what you mean by "legacy reference" all changes are listed with appropriate version numbers since initial creation of project. can you be more specific on what you mean. the dates you mention can be found on release section on main repo it only goes up to version 1.5.1 at this time.

@qriff
Copy link
Author

qriff commented Aug 9, 2018

My bad, there are not release dates attached to the version number, resulting in unclarity when the app has been updated / when to "expect" following updates.

@russhaun
Copy link

russhaun commented Aug 9, 2018

ok i undestand what you mean now. will see if i can address this in a future update and add what you requested. there is no cadence to when updates are released as far as i know maybe that can be worked in. i do not control when updates are released on this repo only my own.

@qriff
Copy link
Author

qriff commented Aug 10, 2018

The cadence is concluded from these changelog version release dates... mainly indicating whether the software is being maintained at all and when to hope for possible fixes

russhaun referenced this issue in russhaun/artillery Jun 2, 2019
updated changelog to include dates on when artillery was updated. related to  issue #56 from BinaryDefense
@russhaun
Copy link

russhaun commented Jun 2, 2019

hey @qriff sorry it took a min. but i just asked for a pull request related to your issue. if you want please look at the updated changelog on my repo and see if the changes i made are what you meant by 'dates for legacy reference'.again sorry for the delay. hope to hear from you

@qriff
Copy link
Author

qriff commented Jun 2, 2019

Perfectly, in line with "~twice a year", including this "issue".
Thank you. =)

@russhaun
Copy link

russhaun commented Jun 4, 2019

this issue can be closed

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

No branches or pull requests

2 participants