You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@zookeeper.apache.org by "Patrick Hunt (JIRA)" <ji...@apache.org> on 2008/07/08 19:06:31 UTC
[jira] Created: (ZOOKEEPER-71) Determine what to do re ZooKeeper
Changelog(s)
Determine what to do re ZooKeeper Changelog(s)
----------------------------------------------
Key: ZOOKEEPER-71
URL: https://issues.apache.org/jira/browse/ZOOKEEPER-71
Project: Zookeeper
Issue Type: Task
Reporter: Patrick Hunt
Assignee: Patrick Hunt
Fix For: 3.0.0
This JIRA is to collect feedback and document what we will be doing re changelog file(s) in zookeeper SVN repository/release.
See ZOOKEEPER-45 for some background, summary:
* suggestion was made to have single CHANGES.txt, similar to hadoop core/hbase
However a concern was brought up that it would be better to have 2 files - one for java code (client & server) and one for C client. This would make it easier for users to discern (C client users would see it broken out in separate file)
Please add comments/votes for what you think we should do.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (ZOOKEEPER-71) Determine what to do re ZooKeeper
Changelog(s)
Posted by "Mahadev konar (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ZOOKEEPER-71?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mahadev konar resolved ZOOKEEPER-71.
------------------------------------
Resolution: Fixed
I just changed the Changes.txt to be a top level file which includes all the jira commits that we make.
> Determine what to do re ZooKeeper Changelog(s)
> ----------------------------------------------
>
> Key: ZOOKEEPER-71
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-71
> Project: Zookeeper
> Issue Type: Task
> Reporter: Patrick Hunt
> Assignee: Mahadev konar
> Fix For: 3.0.0
>
>
> This JIRA is to collect feedback and document what we will be doing re changelog file(s) in zookeeper SVN repository/release.
> See ZOOKEEPER-45 for some background, summary:
> * suggestion was made to have single CHANGES.txt, similar to hadoop core/hbase
> However a concern was brought up that it would be better to have 2 files - one for java code (client & server) and one for C client. This would make it easier for users to discern (C client users would see it broken out in separate file)
> Please add comments/votes for what you think we should do.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-71) Determine what to do re ZooKeeper
Changelog(s)
Posted by "Patrick Hunt (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ZOOKEEPER-71?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Patrick Hunt updated ZOOKEEPER-71:
----------------------------------
Assignee: Mahadev konar (was: Patrick Hunt)
Move all of the changelog related files up to the toplevel (child of trunk) and have sections in the document for java/c clients & java server (and any other major areas that warrant it).
> Determine what to do re ZooKeeper Changelog(s)
> ----------------------------------------------
>
> Key: ZOOKEEPER-71
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-71
> Project: Zookeeper
> Issue Type: Task
> Reporter: Patrick Hunt
> Assignee: Mahadev konar
> Fix For: 3.0.0
>
>
> This JIRA is to collect feedback and document what we will be doing re changelog file(s) in zookeeper SVN repository/release.
> See ZOOKEEPER-45 for some background, summary:
> * suggestion was made to have single CHANGES.txt, similar to hadoop core/hbase
> However a concern was brought up that it would be better to have 2 files - one for java code (client & server) and one for C client. This would make it easier for users to discern (C client users would see it broken out in separate file)
> Please add comments/votes for what you think we should do.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.