I put in the fix version after commit as well. In fact, in SOLR-11876, someone had put in a fix version involving a backport before I committed (which I didn't notice) and I resolved it without actually backporting. It caused a confusion, and resulted in a backport release to go out without the fix. ☹️
On Sun, 2 Jun, 2019, 8:29 PM Erick Erickson, <[email protected]> wrote: > bq. Currently we tag issues with fixVersion before commit, to indicate > what BRANCHES we intend to commit to > > I don’t ;). In fact, I’d favor requiring this to be blank until a fix is > committed. There are, as you’ve found, far too many instances where it’s > filled in and completely inaccurate. > > What I prefer to put in the fixVersion is the version numbers of all the > branches I ported the fix to. There are things we put in, say, 8x that > never get into the next major version. How would we know which ones those > are? > > Can the build tool get clever with a query about requiring the JIRA to be > closed before using fixVersion at all? > > Erick > > > On Jun 1, 2019, at 11:58 AM, Jan Høydahl <[email protected]> wrote: > > > > Currently we tag issues with fixVersion before commit, to indicate what > BRANCHES we intend to commit to > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
