You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafodion.apache.org by "Steve Varnau (JIRA)" <ji...@apache.org> on 2016/06/09 17:16:20 UTC

[jira] [Closed] (TRAFODION-2005) Packaging for patch releases should indicate which packages are changed

     [ https://issues.apache.org/jira/browse/TRAFODION-2005?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Steve Varnau closed TRAFODION-2005.
-----------------------------------
    Resolution: Won't Fix

Just need to document in release notes which packages have functional changes.

> Packaging for patch releases should indicate which packages are changed
> -----------------------------------------------------------------------
>
>                 Key: TRAFODION-2005
>                 URL: https://issues.apache.org/jira/browse/TRAFODION-2005
>             Project: Apache Trafodion
>          Issue Type: Bug
>          Components: Build Infrastructure
>            Reporter: Steve Varnau
>            Assignee: Steve Varnau
>            Priority: Minor
>
> For major and minor releases, the release version number should be the same for every packaged component (installer, server, clients). But for patch releases, it would be good to know if only clients changed, only server, or both.  
> We should always package everything, so that for 2.0.3 release, all packages are provided, but individual packages would have specific patch level when last changed. So I know whether to reinstall server side if upgrading 2.0.0 or 2.0.2.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)