Re: DISCUSS: Optionality of JIRA issues

2024-03-24 Thread Ilan Ginzburg
I do like having a place where a discussion can be had on a code change. Years later it helps. Also, some Jiras get comments or questions long after the code has been merged. If people find that it really slows them down to create a jira, we can create a catch-all jira per released Solr version, r

Re: DISCUSS: Optionality of JIRA issues

2024-03-24 Thread David Smiley
On Sun, Mar 24, 2024 at 6:54 AM Ilan Ginzburg wrote: > > I do like having a place where a discussion can be had on a code change. > Years later it helps. Also, some Jiras get comments or questions long after > the code has been merged. Maybe you mean *in advance of* a code change; i.e. to discuss

Re: DISCUSS: Optionality of JIRA issues

2024-03-24 Thread Gus Heck
I definitely prefer to have a real description of what is intended, and a clear place for status and reporting of fix versions and the like for any "substantive" change. Also a central place to subscribe to hear what people say, or learn when things are addressed/decided I also really don't want to