You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@zookeeper.apache.org by "Michi Mutsuzaki (JIRA)" <ji...@apache.org> on 2014/03/28 05:09:17 UTC

[jira] [Commented] (ZOOKEEPER-297) centralize version numbering in the source/build

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

Michi Mutsuzaki commented on ZOOKEEPER-297:
-------------------------------------------

Diego, sorry for keeping this issue for so long, and thank you for updating the patch so quickly. I'll review the patch tomorrow.

> 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.5.0
>
>         Attachments: build_version.patch, build_version.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
(v6.2#6252)