Julian,
Please refrain from insisting that others should follow the
manual procedures you create.
If you want to have certain manual steps for your own safety, that is fine.
However, don't expect the others will be following all the manual steps you
invent.
I suggest we gather a meetup to discuss exactly that.
I believe it hurts the community A LOT when people object without providing
better alternatives.
I believe it hurts the community when people try solving **non-existing**
issues (see [3]).
I believe it hurts the community when people keep saying "why change, it
works for me" and ignore all the justifications.
I believe it hurts the community when people object over a triviality.
Please, take it seriously.
I do not really want to see the story of "key committers leaving the
project as it happened in log4j 1.x, Mina, etc"
Do you want to see "latest tested Java at the Calcite website"?
Nice. Why don't you make the version appear automatically on all the pages
that need it?
If you lack time, why don't you ask somebody to volunteer on that?
What is the point of asking people doing manual steps and blaming me and
Rui for
inaccurate following the steps you created?
----
We followed your suggestions, and we are here: I forgot editing howto, and
Rui missed it as well.
Could you please understand adding manual steps NEVER really solves the
"documentation being stale" issue?
Julian>you were not prepared to accept simple solutions
Your suggestion regarding howto.md is not a solution, so I am not prepared
to accept non-solutions.
I suggested multiple trivial (!) proposals to keep the documentation
**always** up to date.
You can ignore them, yet, please don't create obscure manual procedures for
others to follow.
A solution in [1]:
Replace "Prerequisite is ... Gradle (version 7.2) on your path"
with "Prerequisite is ... Gradle (see version in
gradle/wrapper/gradle-wrapper.properties) on your path"
^^ single line change yielding always up-to-date documentation, and it
works for ALL Calcite versions, including the past ones.
Note: there's no harm in keeping gradle-wrapper.properties in the source
release, so
A solution in [2]:
Replace "Prerequisite is ... Gradle (version 7.2) on your path"
with "Prerequisite is ... Gradle {% gradle_version_from_wrapper_properties
%}"
The value should be replaced automatically when building the site.
It might look slightly better on a website, however, it would be slightly
misleading.
If someone tries building a slightly old Calcite version, they would need
to use
a different Java/Gradle version.
---
In the ideal world, the thing should be buildable automatically, or
there should be a small README that explains which tools do you need to be
installed.
I do not really expect people to use howto.md for building from the source
archive.
[1]
https://issues.apache.org/jira/browse/CALCITE-4575?focusedCommentId=17339990&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-17339990
[2] https://lists.apache.org/thread/mdxdosofclqbp9p5osflwtor264757m4
[3]
https://issues.apache.org/jira/browse/CALCITE-4575?focusedCommentId=17340320&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-17340320
Vladimir
