…instead of in .travis.yml (#5)

TICKET =
LI_DESCRIPTION =

EXIT_CRITERIA = MANUAL ["describe exit criteria"]

TICKET =
LI_DESCRIPTION =

Add build changes to publish github LinkedIn Kafka artifacts to bintray (#1)
[NOTE] This is a temporary measure to publish artifacts until CI is properly set up to do the job automatically. Users are not expected to run this themselves.

Add changes for CI builds and publishing artifacts to bintray. (#2)
Travis will kick off a build and publish artifacts to bintray upon creating a tag in the "x.y.z.w" format.

Try different encrypted bintray-related env variables for Travis (#4)
Travis couldn't access one of the initially encrypted variables for some reason.

Set Bintray-related env variables via repository setting instead of in .travis.yml (#5)

Use the maven repo under the LinkedIn Bintray account to publish artifacts (#25)

EXIT_CRITERIA = MANUAL [""]

The LICLOSEST enum constant was dropped in the PR #538 squash, breaking
LI consumer configs of the form auto.offset.reset=licloasest at enum
parse time (IllegalArgumentException at OffsetResetStrategy.valueOf).

In 3.0-li, LICLOSEST was a config-surface-only addition (LIKAFKA-18568):
the enum value existed but no consumer logic special-cased it. The
fall-through behavior was equivalent to NONE for both the timestamp-
based reset path (Fetcher.offsetResetStrategyTimestamp returns null)
and the request-reset path. Restoring the enum constant alone is
therefore sufficient to fix the parse-time failure and preserve 3.0-li
behavior bit-for-bit.

Updated AUTO_OFFSET_RESET_DOC accordingly so operators see the option
in the config docs.

The LICLOSEST enum constant was dropped in the PR #538 squash, breaking
LI consumer configs of the form auto.offset.reset=licloasest at enum
parse time (IllegalArgumentException at OffsetResetStrategy.valueOf).

In 3.0-li, LICLOSEST was a config-surface-only addition (LIKAFKA-18568):
the enum value existed but no consumer logic special-cased it. The
fall-through behavior was equivalent to NONE for both the timestamp-
based reset path (Fetcher.offsetResetStrategyTimestamp returns null)
and the request-reset path. Restoring the enum constant alone is
therefore sufficient to fix the parse-time failure and preserve 3.0-li
behavior bit-for-bit.

Updated AUTO_OFFSET_RESET_DOC accordingly so operators see the option
in the config docs.