Since we track releases in JIRA, the contributors are listed there. I'm in favor of moving this stuff to github through the new Apache/Github integration, but we just haven't done that yet.
On Mon, Nov 13, 2017 at 9:02 AM, Zoltan Ivanfi <z...@cloudera.com> wrote: > I can see the value of setting the assignee while working on an issue (so > that the ongoing effort is clearly visible, which helps avoiding wasted > effort), but what is purpose of setting the assignee after the JIRA is > fixed? The commit itself (referenced from the JIRA as well) clearly > identifies the author. > > I really like this aspect of the merge script that it handles both git and > JIRA at the same time. > > Thanks, > > Zoltan > > On Mon, Nov 13, 2017 at 5:55 PM Ryan Blue <rb...@netflix.com.invalid> > wrote: > >> I've marked format-2.4.0 released in JIRA. Thanks for pointing out that it >> hadn't been done. >> >> For the PR merge script, please don't use it to close issues. In fact, we >> should remove that. Part of closing an issue is making sure the >> contributor >> is assigned the issue in JIRA, but the script can't do that. I always opt >> to go close the issue by hand and take care of this through the web UI. >> >> rb >> >> On Mon, Nov 13, 2017 at 5:04 AM, Zoltan Ivanfi <z...@cloudera.com> wrote: >> >> > Hi, >> > >> > When resolving JIRAs using the dev/merge_parquet_pr.py script, one has >> to >> > specify a fix version, otherwise the script will use format-2.4.0, >> which is >> > already released. There is no good choice for the fix version as >> > format-2.4.0 is the largest version number JIRA knows about (and in >> fact it >> > lists it as an unreleased version). >> > >> > I would have two questions: >> > - What version number should be added as the next unreleased version? >> > - Who can edit the version numbers in JIRA? >> > >> > Thanks, >> > >> > Zoltan >> > >> >> >> >> -- >> Ryan Blue >> Software Engineer >> Netflix >> > -- Ryan Blue Software Engineer Netflix
