* re-sent after sending the first one with the wrongsender*
i'm planning to add town-crier support to the "guess next version" logic
of setuptools_scm
based on your pre-commit + potentially push action im hoping to provide
2 extra actions to provide better
release automation
a) regendoc autoproposal -> opens a pr when regendoc changes happen,
updates it when new commits come in without merge
b) next release proposal/merge -> runs town crier with the next version
specified and publishes a branch/pr, auto-merges when a tagged version
of that pr is deployed to pypi
As part of implementing this proposal i would update the related
documentation
-- Ronny
Am 25.11.19 um 18:13 schrieb Anthony Sottile:
I would also be ok with removing the master/features setup -- I think
a few things would have to be carefully considered as part of
releasing though:
- some sort of marker to indicate (maybe just based on changelog
filenames?) that a minor / patch / major release would be next
- an overhaul of the various related documentation (how to release, PR
changelog, probably some other stuff I'm forgetting about)
I think as a result we'd also want to release more often (which I'm
also not against).
Anthony
_______________________________________________
pytest-dev mailing list
pytest-dev@python.org
https://mail.python.org/mailman/listinfo/pytest-dev
_______________________________________________
pytest-dev mailing list
pytest-dev@python.org
https://mail.python.org/mailman/listinfo/pytest-dev
