[
https://issues.apache.org/jira/browse/KAFKA-4450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15840900#comment-15840900
]
ASF GitHub Bot commented on KAFKA-4450:
---------------------------------------
GitHub user ewencp opened a pull request:
https://github.com/apache/kafka/pull/2457
KAFKA-4450: Add upgrade tests for 0.10.1 releases and rename TRUNK to
CURRENT_BRANCH to reduce confusion.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ewencp/kafka kafka-4450-upgrade-tests
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/kafka/pull/2457.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #2457
----
commit b0d74ef691214010ecfa4c0e27283fdc2373f4b4
Author: Ewen Cheslack-Postava <m...@ewencp.org>
Date: 2017-01-26T18:45:06Z
KAFKA-4450: Add upgrade tests for 0.10.1 releases and rename TRUNK to
CURRENT_BRANCH to reduce confusion.
----
> Add missing 0.10.1.x upgrade tests and ensure ongoing compatibility checks
> --------------------------------------------------------------------------
>
> Key: KAFKA-4450
> URL: https://issues.apache.org/jira/browse/KAFKA-4450
> Project: Kafka
> Issue Type: Bug
> Components: system tests
> Affects Versions: 0.10.1.0
> Reporter: Ewen Cheslack-Postava
> Assignee: Ewen Cheslack-Postava
> Priority: Blocker
> Fix For: 0.10.2.0
>
> Original Estimate: 72h
> Remaining Estimate: 72h
>
> We have upgrade system tests, but we neglected to update them for the most
> recent released versions (we only have LATEST_0_10_0 but not something from
> 0_10_1).
> We should probably not only add these versions, but also a) make sure some
> TRUNK version is always included since upgrade to trunk would always be
> possible to avoid issues for anyone deploying off trunk (we want every commit
> to trunk to be solid & compatible) and b) make sure there aren't gaps between
> versions annotated on the test vs versions that are officially released
> (which may not be easy statically with the decorators, but might be possible
> by checking the kafkatest version against previous versions and checking for
> gaps?).
> Perhaps we need to be able to get the most recent release/snapshot version
> from the python code so we can always validate previous versions? Even if
> that's possible, is there going to be a reliable way to get all the previous
> released versions so we can make sure we have all upgrade tests in place?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
