If you've already done the work, then I'd say by all means, go ahead and submit (just as I had already started the work of Image.getBaseline()). We'll have plenty of time to make sure it's stable. Let's all just turn our collective effort towards stabilizing the code base after we're done committing our work-in-progress.
On Wed, Nov 18, 2009 at 1:41 AM, Noel Grandin <[email protected]> wrote: > Is it OK if I commit my TableView variableRowHeight code? > > It's a pretty straightforward port of the variableItemHeight code from > ListView. > > -- Noel > > Greg Brown wrote: > > I am thinking that we should impose a feature freeze once the > > remaining tickets for 1.4 have been resolved. Here is what is > > currently outstanding: > > > > PIVOT-205 Pivot collections test suite > > > > I think we can safely push this back to 1.41. > > > > PIVOT-235 Complete tutorial > > > > This one is nearly complete. There are only 2 or 3 remaining sections, > > and I think we should push to wrap this up for 1.4. This was one of > > our primary focuses for 1.4, and it will be even more important to > > have solid documentation should we graduate to a TLP. So we should > > make sure we finish this one. > > > > PIVOT-23 Ensure that popups are constrained to display bounds > > > > I think this can safely be deferred to 1.4.1. > > > > PIVOT-43 Add support for digest authentication to web queries > > > > I suggest that we move this to 1.4.1 as well. > > > > That would leave the tutorial docs as the only outstanding item. > > > > Any objections? > > > > G > > > >
