Preparing for 2.5

0 views
Skip to first unread message

David Huynh

unread,
Aug 31, 2011, 12:19:30 PM8/31/11
to google-r...@googlegroups.com
Hi all,

I'm thinking about a 2.5 release in the near future (1 - 2 months?). It will mostly be about the new importer UIs and the custom tabular exporter UI, and I'd love some help testing them exhaustively. E.g., importing multiple files and archive files is especially tricky. Please also let me know if there is anything missing, either regressions from 2.1 importing features or new features that would make sense in these new UIs.

Also, please tag any existing issue with Milestone 2.5 if you think it's crucial to get fixed.

Thanks!

David

Tom Morris

unread,
Sep 1, 2011, 6:44:58 PM9/1/11
to google-r...@googlegroups.com
On Wed, Aug 31, 2011 at 12:19 PM, David Huynh <dfh...@gmail.com> wrote:

> I'm thinking about a 2.5 release in the near future (1 - 2 months?).

That sounds like a good plan. Having more frequent releases will help
maintain momentum.

> It will mostly be about the new importer UIs and the custom tabular exporter UI,

I *love* the new importer framework. I used the "create from
clipboard" option constantly. I'm converting my OpenOffice Calc
importer over and hope to have it available to include in the release.

> I'd love some help testing them exhaustively. E.g., importing multiple files
> and archive files is especially tricky.

I think the only way we're going to get the coverage we need is from
beta users. It'll be good to shake out as many problems as we can
ourselves first, but we should plan on a long enough beta period to
allow some serious testing.

Tom

Thad Guidry

unread,
Sep 1, 2011, 6:52:59 PM9/1/11
to google-r...@googlegroups.com

> I'd love some help testing them exhaustively. E.g., importing multiple files
> and archive files is especially tricky.

I think the only way we're going to get the coverage we need is from
beta users.  It'll be good to shake out as many problems as we can
ourselves first, but we should plan on a long enough beta period to
allow some serious testing.

Tom

Agreed with Tom, we should, at a minimum, cover 2 weeks (2 full weekends) for folks to beta test it.

--
-Thad
http://www.freebase.com/view/en/thad_guidry

David Huynh

unread,
Sep 1, 2011, 9:12:16 PM9/1/11
to google-r...@googlegroups.com
I'm all for more testing!

How about having people on the google-refine-dev@ test out trunk/ for 2 weeks, then we cut an RC1 and have people on google-refine@ test it out for another 2 weeks?

Thanks,

David

Thad Guidry

unread,
Sep 1, 2011, 9:36:07 PM9/1/11
to google-r...@googlegroups.com
On Thu, Sep 1, 2011 at 8:12 PM, David Huynh <dfh...@gmail.com> wrote:
I'm all for more testing!

How about having people on the google-refine-dev@ test out trunk/ for 2 weeks, then we cut an RC1 and have people on google-refine@ test it out for another 2 weeks?

Thanks,

David

 
+1 Perfect Idea.  2 weeks devs + 2 weeks public beta
 
--
-Thad
http://www.freebase.com/view/en/thad_guidry
Reply all
Reply to author
Forward
0 new messages