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

get_releases.py should default to more than 30 days #4

Open
chriscool opened this issue Jun 18, 2018 · 3 comments
Open

get_releases.py should default to more than 30 days #4

chriscool opened this issue Jun 18, 2018 · 3 comments

Comments

@chriscool
Copy link
Owner

chriscool commented Jun 18, 2018

There can be more than 30 days between 2 Git Rev News editions, so 30 days may make us miss some releases.

It's better to get releases that we already talked about rather than miss releases, so I suggest a 40 or 45 days default rather than 30.

This is a follow up from #3.

@gaalcaras

@chriscool
Copy link
Owner Author

Also we often prepare the releases on Saturday or Sunday, and we publish the next Wednesday, so there is already a potential window for missing releases.

@gaalcaras
Copy link
Contributor

Okay, I'll change the default settings.

we publish the next Wednesday, so there is already a potential window for missing releases.

Once the script gets more reliable, maybe a solution would be to generate the releases section when RevNews is published? Could also tie in with git/git.github.io#273

@gaalcaras
Copy link
Contributor

Another thing we could do is being clear about the period in which the releases occured. Maybe something like:

# Releases

The following releases were issued between 2018-04-01 and 2018-05-01:

+ ...

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