Issue templates

[John Cremona]

I was about to open a new issue for work I have done which will implement a greatly improved method for something already implemented in Sage (twice, both by me...).  When you click on the button to create a new issue, there are three categories listed: Bug Report, Failure Building from Source, and Feature request -- plus a catch-all "blank issue".

Surely my situation is common enough to warrant an additional template, called (say) "Improvement on existing code"?

Also, there should be something for upgrading a dependent package.

Meanwhile I'll use the blank issue.

John

[Dima Pasechnik]

if you already have the code, a PR would do, no need for an issue, IMHO.

> --
> You received this message because you are subscribed to the Google Groups "sage-devel" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/sage-devel/CAD0p0K6uPy5CfYt7M21CrR8HuETfCTH%2B7kMknBTpN74cC503tg%40mail.gmail.com.

[John Cremona]

On Thu, 16 Feb 2023 at 10:18, Dima Pasechnik <dim...@gmail.com> wrote:

if you already have the code, a PR would do, no need for an issue, IMHO.

Good point.  But between some stand-alone code and properly integrating the functionality into Sage takes time and effort (which I am now in the middle of), and I might get distracted before finishing...

 

To view this discussion on the web visit https://groups.google.com/d/msgid/sage-devel/CAAWYfq2_cG0Sw3_BrjhHLCs2EEH2o-5f1-Z9bY-PAZEytHCm2g%40mail.gmail.com.

[Ricardo Buring]

Another option would be to open a pull request as a draft (with initial changes in any state of completion, which can anyway be overwritten later using a force push). The draft state (which can be chosen when opening a PR, and can be toggled afterward as well) blocks the PR from being merged and allows it to be marked ready later.