[jira] [Commented] (DERBY-6551) Test upgrade from release branches and release candidates to trunk

["Knut Anders Hatlen (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/DERBY-6551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13980809#comment-13980809 ] 

Knut Anders Hatlen commented on DERBY-6551:
-------------------------------------------

Rick has added this to the [Release Vetting Checklist|https://wiki.apache.org/db-derby/ReleaseVettingChecklist]. Thanks!

> Test upgrade from release branches and release candidates to trunk
> ------------------------------------------------------------------
>
>                 Key: DERBY-6551
>                 URL: https://issues.apache.org/jira/browse/DERBY-6551
>             Project: Derby
>          Issue Type: Task
>          Components: Test
>    Affects Versions: 11.0.0.0
>            Reporter: Knut Anders Hatlen
>
> We currently have good automated tests for upgrade from already released versions to the next version to be released. What we don't test regularly, is that upgrade from the next version to be released works. If there's a problem with that upgrade path, we typically won't detect it until after the next version has been released and added as a starting point for the upgrade tests on trunk.
> It would be good if we ran tests that verified that release candidates could be upgraded from, before we have actually released them. At the very least, we should add an item to the release checklist as a reminder to run such an upgrade test (from the release candidate to trunk) manually.
> It would be even better if we could set up a job on builds.apache.org that automatically tested upgrade from the head of the most recent release branch (or branches) to trunk to give us an early warning when an upgrade problem is introduced.



--
This message was sent by Atlassian JIRA
(v6.2#6252)