impala-reviews mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Brown (Code Review)" <ger...@cloudera.org>
Subject [Impala-ASF-CR] [DOCS] Include the current Impala version number on PDF title page
Date Mon, 27 Nov 2017 21:44:07 GMT
Michael Brown has posted comments on this change. ( http://gerrit.cloudera.org:8080/8648 )

Change subject: [DOCS] Include the current Impala version number on PDF title page
......................................................................


Patch Set 1:

> I wonder though do we need the ability to let the docs run at a
 > slightly different schedule than the code.

I would prefer the docs to be ready for release alongside the code, not after. I don't agree
with continually punting on releasing docs on time. Mechanisms like "allow us to make updates
to 2.10 docs from master" help ensure that docs may always run late.

>  For example, today or tomorrow I want to republish the 2.10 docs to account for the
removal of "incubating".

Why? 2.10 was released weeks ago, when Impala was still incubating.

Also, why publish 2.10 docs updates from master in the first place? Shouldn't that come from
a branch off branch-2.10? (I can imagine sometimes that this is necessary: correcting errata,
for instance.)


-- 
To view, visit http://gerrit.cloudera.org:8080/8648
To unsubscribe, visit http://gerrit.cloudera.org:8080/settings

Gerrit-Project: Impala-ASF
Gerrit-Branch: master
Gerrit-MessageType: comment
Gerrit-Change-Id: I66d6669769d2aa22602057bfcf5b29307e2a0fa2
Gerrit-Change-Number: 8648
Gerrit-PatchSet: 1
Gerrit-Owner: John Russell <jrussell@cloudera.com>
Gerrit-Reviewer: Jim Apple <jbapple-impala@apache.org>
Gerrit-Reviewer: John Russell <jrussell@cloudera.com>
Gerrit-Reviewer: Laurel Hale <laurel@cloudera.com>
Gerrit-Reviewer: Michael Brown <mikeb@cloudera.com>
Gerrit-Comment-Date: Mon, 27 Nov 2017 21:44:07 +0000
Gerrit-HasComments: No

Mime
  • Unnamed multipart/alternative (inline, 8-Bit, 0 bytes)
View raw message