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 wrote:
> I can see the value of setting
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
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
[
https://issues.apache.org/jira/browse/PARQUET-1145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zoltan Ivanfi updated PARQUET-1145:
---
Fix Version/s: (was: format-2.4.0)
> Add license to .gitignore and .travis.yml
>
[
https://issues.apache.org/jira/browse/PARQUET-1145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zoltan Ivanfi resolved PARQUET-1145.
Resolution: Fixed
Fix Version/s: format-2.4.0
Issue resolved by pull request 75
[
https://issues.apache.org/jira/browse/PARQUET-654?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16249333#comment-16249333
]
Hyukjin Kwon commented on PARQUET-654:
--
Hi [~rdblue], Is it backported to 1.8.2 as well? Looks I am