Please vote on this Apache Phoenix Tephra release candidate,
phoenix-tephra-0.16.0RC2
The VOTE will remain open for at least 72 hours.
[ ] +1 Release this package as Apache phoenix tephra 0.16.0
[ ] -1 Do not release this package because ...
The tag to be voted on is 0.16.0RC2
https://github.
Should we just incorporate the omid and tephra websites into phoenix.a.o
going forward?
I'm surprised infra didn't kill the old websites when the IPMC
"graduated" them.
ASF websites are either updated via svn pub-sub, git pub-sub, or via ASF
CMS (which might be EOL, I forget).
svn/git pub-
+1 (binding)
* xsums/sigs OK
* CHANGES has reasonable content
* mvn apache-rat:check passes and `find . -type f` doesn't show anything
unreasonable
* Can build the code
* Ran many unit tests, but cancelled at ~1hr mark.
* Can build Phoenix master against 0.16.0rc2
On 11/30/20 8:15 AM, Istvan T
[
https://issues.apache.org/jira/browse/PHOENIX-5860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chao Wang updated PHOENIX-5860:
---
Attachment: PHOENIX-5860-4.x.002.patch
> Throw exception which region is closing or splitting when
Hi all,
It's time to discuss the Phoenix 4.16 release. After many people's
contributions on the bug fixes, new features, and other works in the past
few months, we are kind of close to the point to have a RC (still need to
fix test flappers). Please let me know if you think any JIRA must be part
o
I did some digging around in the meantime.
Omid seems to use the mechanism where the site is simply pulled from the
git repo.
We should be able to have it automagically deploy it into a phoenix.a.o
subdirectory by adding an .asf.yaml file in the phoenix-omid-site repo.
The Tephra website also loo
