Mailing-List: contact avro-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: avro-dev@hadoop.apache.org
Message-ID: <2106278541.1254775051447.JavaMail.jira@brutus>
Date: Mon, 5 Oct 2009 13:37:31 -0700 (PDT)
From: "Doug Cutting (JIRA)" <jira@apache.org>
To: avro-dev@hadoop.apache.org
Subject: [jira] Commented: (AVRO-133) The Avro spec must be change
 controlled
In-Reply-To: <1988694971.1254762751280.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/AVRO-133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12762353#action_12762353 ] 

Doug Cutting commented on AVRO-133:
-----------------------------------

> For example, when I print a pdf copy of the spec, the only thing that indicates a version is the title "Avro 1.0 Specification"

Ah, right, that needs to get updated.

Currently I update by hand the version in the tab ("Avro X.X.X Documentation"), as directed in:

http://wiki.apache.org/hadoop/Avro/HowToRelease

but I neglected the version in the spec page itself.

Ideally we could get the version from the build, so that we only specify it in a single place.

> The Avro spec must be change controlled
> ---------------------------------------
>
>                 Key: AVRO-133
>                 URL: https://issues.apache.org/jira/browse/AVRO-133
>             Project: Avro
>          Issue Type: Bug
>          Components: spec
>            Reporter: Jon Bratseth
>
> It seems currently changes are being made without bumping the version number.
> The spec should:
> - Change minor number each time any change is made
> - Include a change log listing each change and accompanying version number

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.