Java summary of current non-blockers: AVRO-738 will close as a result of AVRO-753. AVRO-730 will likely make it in. AVRO-726 I'll try and get to this, but only after the top 3 blockers are done. AVRO-761 Its close, but does not break APIs so is safe for a 1.5.1 if we run out of time. We should mark this for 1.5.1 if we can't get to it. I marked it with 1.5.0 for now (non-blocker) so its on our radar.
spec related items, these will most likely end up assigned to 1.6.0. Note, a 1.5.1 release can happen fairly quickly afterwards. 1.5.0 is the hard one because a couple languages have some significant API changes. On 2/17/11 11:35 AM, "Doug Cutting" <[email protected]> wrote: >The list of currently unresolved issues targeted for 1.5 is at: > >http://tinyurl.com/4asjh64 > >In the interest of ushering 1.5 out the door sooner rather than later, >let's mark things that we should hold the release for as "Blocker". > >I propose to remove all non-blockers from this 1.5 list on Monday, >February 21. Does anyone object? > >If you feel strongly that an issue should block the 1.5.0 release and >are willing to work on it to make sure that it can be committed soon, >please change it to blocker. API changes should be the highest >priority, since the 1.5.0 release will establish API compatibility for >all subsequent 1.5.x bugfix releases. > >I already marked a few issues as blockers. > >Thanks! > >Doug
