Home | About | Sematext search-lucene.com search-hadoop.com
 Search Hadoop and all its subprojects:

Switch to Threaded View
Avro >> mail # dev >> 1.4.0 release soon?


Copy link to this message
-
Re: 1.4.0 release soon?
+1 on prior to branching 1.4, revert trunk/lang/c to branch-1.3/lang/c.

Is it possible to make the current trunk a devel branch before reverting for
Bruce and I to finish up the work and merge into 1.4 later?

--
Matt

*Hadoop World 2010 -- October 12 | New York -- **Register
today!*<http://www.cloudera.com/company/press-center/hadoop-world-nyc/>

On Tue, Aug 24, 2010 at 12:07 PM, Doug Cutting <[EMAIL PROTECTED]> wrote:

> On 07/19/2010 03:44 PM, Bruce Mitchener wrote:
>
>> Avro C is in bad shape / a bad state. It was in the middle of some
>> breaking API changes (and more are needed).
>>
>> It is probably better to look at reverting some of the changes and
>> just shipping what was in 1.3.x (even though the API there is not
>> complete and one can't actually use it for much).
>>
>
> The changes to lang/c since 1.3 was branched can be listed with:
>
> svn log -r 927600:HEAD lang/c
>
> There have been no lang/c changes merged to the 1.3 branch.
>
> The changes in trunk sound incomplete.  I see two options:
>  - prior to branching 1.4, revert trunk/lang/c to branch-1.3/lang/c; or
>  - after branching 1.4, revert branch-1.4/lang/c to branch-1.3/lang/c
>
> My preference is to keep trunk releasable, so I prefer the former.  We'd
> then re-open the Jira issues that were closed.  If someone wants to continue
> the effort started, they can revive the reverted changes in a feature branch
> and merge them to trunk when they're releasable.
>
> Does that sound reasonable?
>
> Doug
>