-
Notifications
You must be signed in to change notification settings - Fork 97
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
How about tagging a new release #330
Comments
Who's in charge of this? |
@flokli what do you think ? |
Sorry, only saw this now. I did #333 recently, because I was getting readthedocs emails, and added a 3.1.0 section in I guess what's needed for this is going through the git commits since |
Things I see so far:
@GuillaumeSeren considering you were involved in most of these PRs, can you take a look and send a PR adding some summaries to NEWS.md? |
Hey, Yes I will prepare a PR with the needed changes in the NEWS.md 📝 |
Maybe we could get #307 as well ? |
With #334 in, I'd say let's cut a release now, and not delay it much further. |
We can still do another release afterwards. |
Sure let's check others patches later and finish this release as it is. |
Apologies if this is a stupid question. Is there anything preventing the tagging of a new release? Maybe anything I can contribute? |
I'm generally not happy with the amount of test coverage in the project, but I fear I also don't have enough capacity to appropriately maintain it, so maybe it's time to put someone else on the helm. @GuillaumeSeren, I invited you to the |
@GuillaumeSeren : How do you resonate with @flokli 's suggestion to adopt the package? |
Hey,
it's been a while since the last release (~2 years since the 3.0.1),
I would like to suggest a new release we had quite some work done,
and the python target used back then have to upgraded to something up-to-date.
What do you think ?
The text was updated successfully, but these errors were encountered: