[
https://issues.apache.org/jira/browse/AVRO-187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Doug Cutting updated AVRO-187:
------------------------------
Affects Version/s: (was: 1.2.0)
(was: 1.1.0)
(was: 1.0.0)
Fix Version/s: (was: 1.2.1)
This is not a regression, so it shouldn't be flagged for potential inclusion in
the 1.2.1 bugfix release (if we ever in fact make such a release). Also, since
it's an "Improvement" it probably doesn't need an "Affects Version".
Also, generally we only mark things as fixed in a single version, either the
next upcoming release, or the release branch we intend to backport it to. We
generally fix things in trunk, including adding a message to CHANGES.txt, then
sometimes backport the patch to a release branch. Things that are backported
should be moved to the section of trunk's CHANGES.txt for the branch they're
backported to. We don't want a change listed twice in CHANGES.txt, since trunk
generally includes all changes listed. So the only time things are marked as
fixed in multiple versions are things that will be backported to multiple
branches. Does that make sense?
> Move top-level source files into separate directories for easier maintenance
> ----------------------------------------------------------------------------
>
> Key: AVRO-187
> URL: https://issues.apache.org/jira/browse/AVRO-187
> Project: Avro
> Issue Type: Improvement
> Components: c
> Reporter: Matt Massie
> Assignee: Matt Massie
> Fix For: 1.3.0
>
> Attachments: AVRO-187.patch
>
>
> This patch separates all top-level source into specific top-level directories
> (e.g. io, tests, datatypes) to make it easier to maintain.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
