On Sun, 5 Jan 2025 at 20:29, Benjamin Marwell wrote:
>
> +1, works well in other projects as well, and if needed, we can always
> extend on that.
> Questions should go to SO (or, maybe, to discussions).
SO can be the next step, now we have a ML.
I would like to enable GitHub Issues for some of t
+1, works well in other projects as well, and if needed, we can always
extend on that.
Questions should go to SO (or, maybe, to discussions).
Am Sa., 4. Jan. 2025 um 22:37 Uhr schrieb Slawomir Jaranowski
:
>
> On Sat, 4 Jan 2025 at 22:28, Matthias Bünger
> wrote:
> >
> > Hi,
> > I personally don
On Sat, 4 Jan 2025 at 22:28, Matthias Bünger wrote:
>
> Hi,
> I personally don't see the benefit of the "improvement" and "new
> feature". Even more I think it might confuse people, especially deciding
> what is an improvement and what is a new feature. Is a feature only new,
> when it's introduci
Hi,
I personally don't see the benefit of the "improvement" and "new
feature". Even more I think it might confuse people, especially deciding
what is an improvement and what is a new feature. Is a feature only new,
when it's introducing anything completly new which wasn't there before
or where's t
Hi,
Working forward on GitHub Issues I would like to propose a templates for issues:
- Bug Report - standard bug report
- New Feature Proposal - request for new feature
- Improvement Proposal - improvement for existing feature
I hope it will be enough ...
So my proposed PR:
- https://github.co