You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@zookeeper.apache.org by "Flavio Junqueira (JIRA)" <ji...@apache.org> on 2014/04/07 11:05:19 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=13961725#comment-13961725 ]
Flavio Junqueira commented on ZOOKEEPER-297:
--------------------------------------------
Any idea what's going on here? Also, [~diegooliveira], please name patches using "ZOOKEEPER-XXXX.patch".
> 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, 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
(v6.2#6252)