zookeeper-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Enrico Olivelli (Jira)" <j...@apache.org>
Subject [jira] [Updated] (ZOOKEEPER-297) centralize version numbering in the source/build
Date Fri, 06 Sep 2019 15:47:03 GMT

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

Enrico Olivelli updated ZOOKEEPER-297:
--------------------------------------
    Fix Version/s:     (was: 3.5.6)

> centralize version numbering in the source/build
> ------------------------------------------------
>
>                 Key: ZOOKEEPER-297
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-297
>             Project: ZooKeeper
>          Issue Type: Improvement
>          Components: build
>    Affects Versions: 3.5.0
>            Reporter: Patrick Hunt
>            Assignee: Diego de Oliveira
>            Priority: Minor
>              Labels: patch
>             Fix For: 3.6.0, 3.5.7
>
>         Attachments: build_version.patch, build_version.patch, build_version2.patch,
build_version3.patch
>
>
> There are now three locations in the source repository that store the version number
of the code:
> 1) build.xml
> 2) configure.ac
> 3) zookeeper_version.h
> these all have to be managed when releasing/branching/etc... would be better if there
were just one place - at the very least the configure.ac should be used to generate the version
for zookeeper_version.h. 
> Can we do a better job (ie less) at this?



--
This message was sent by Atlassian Jira
(v8.3.2#803003)

Mime
View raw message