Thanks Stamatis! So far I think I like pretty much every alternative
I've seen more than the current logo. I'm not sure what others think
about process, but I'd like to close discussion and take a vote in the
near future.
--
Michael Mior
mm...@apache.org
Le lun. 24 juin 2019 à 17:37, Stamatis Zam
FWIW, the following one-liner did most of the work for me
git log --format='format:%s' branch-1.19..branch-1.20 | sed
"s_\(CALCITE-[0-9]\+\)_\1_"
--
Michael Mior
mm...@apache.org
Le lun. 24 juin 2019 à 20:34, Francis Chuang
a écrit :
>
> +1 to using a script to auto-generate a draft of the rele
+1 to using a script to auto-generate a draft of the release notes. I
was just thinking about this a few days ago, considering that there were
more than 100 changes in this release.
A script to generate each log item (with the correct link to the JIRA
issue) would allow the RM to focus on cate
I've added back the names and I'm redeploying the site now. I think
I've said this before, but I don't really see the point of adding
contributor names into commit messages when they are already recorded
as the author of the commit. If the commit needs to be edited or
rebased, the author can be pre
In my opinion, we should add back the names to 1.20’s release notes.
For further releases (and future commits), I’m happy to have a discussion about
our policy of adding names of non-committer contributors to commit messages and
release notes. It is, after all, somewhat unusual and rather onerou
I added a couple of more alternatives under [1]. Let me know what you
think.
More suggestions are very welcome!
Best,
Stamatis
[1] https://github.com/zabetak/calcite/tree/calcite-logo/site/img
On Wed, Jun 5, 2019 at 4:47 AM Yuzhao Chen wrote:
> I would prefer
> https://github.com/zabetak/calci
I think the rotation is working out alright except that it's a
challenging sticking to a time-based schedule.
As far as the release notes, you're correct that I generated these
from the commit log. I actually intentionally stripped out the names
since at the time they felt like noise. I'll acknow
Steven Talbot created CALCITE-3145:
--
Summary: Aggregate duplicate detection bug with group fields
Key: CALCITE-3145
URL: https://issues.apache.org/jira/browse/CALCITE-3145
Project: Calcite
I
Julian Hyde created CALCITE-3144:
Summary: Add rule, CaseFilteredAggregatorRule, that converts
"SUM(CASE WHEN b THEN x END)" to "SUM(x) FILTER (WHERE b)"
Key: CALCITE-3144
URL: https://issues.apache.org/jira/brows
Just back for vacation... and it’s great to see a shiny new release. Thank you,
Michael, for getting it out of the door.
Release management is a huge task these days. A few months ago [1] we agreed a
rotation of release managers for a few releases ahead. I think this is working
well; it makes s
Thanks to everyone who has tested the release candidate and given
their comments and votes.
The tally is as follows.
4 binding +1s:
Michael Mior
Francis Chuang
Vladimir Sitnikov
Stamatis Zampetakis
4 non-binding +1s:
Haisheng Yuan
Hongze Zhang
Andrei Sereda
Chunwei Lei
No 0s or -1s.
Therefore
Great. I'll roll out the release shortly and we can fix after. I think
switching to an Apache licensed alternative is probably easiest.
On Mon, Jun 24, 2019, 10:06 Vladimir Sitnikov
wrote:
> As far as I see, the fonts in question are a part of source release since
> 2015-05, so I don't think we
As far as I see, the fonts in question are a part of source release since
2015-05, so I don't think we should veto 1.20.
The fonts in question are not crucial for Calcite operation, so my vote is
still +1.
Vladimir
Li Xian created CALCITE-3143:
Summary: Dividing NULLIF clause may cause Division by zero error
Key: CALCITE-3143
URL: https://issues.apache.org/jira/browse/CALCITE-3143
Project: Calcite
Issue Typ
14 matches
Mail list logo
