New OpenRefine v2.6 smoke test kits available

[Tom Morris]

I've built new kits from the current development sources and uploaded them to Github.

https://github.com/OpenRefine/OpenRefine/releases/tag/v2.6-rc1

Although they're labeled RC1, they are not real release candidates, but more like a quick checkpoint to allow us to verify all the fixes that have been made since beta 1 and figure out what remaining loose ends need to be cleaned up.

Please take them time to do some testing and provide feedback.  If you can help with updating the issue tracker as well, that would be very useful.

Tom

[Thad Guidry]

Tom
I will try to run through some testing tonight.
Thanks for triage and building!

--
You received this message because you are subscribed to the Google Groups "OpenRefine Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email to openrefine-de...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Martin Magdinier]

Tom,

Thanks for putting the RC-1 together.

Should we take this as an opportunity to finish the branding change? The only things left is renaming Google Refine Expression Language to General Refine Expression Language.

If other committers / contributors are ok with this change,  change is ready for merge here: https://github.com/OpenRefine/OpenRefine/pull/982

Will do some testing on the RC-1

Martin

[Tom Morris]

On Thu, Apr 30, 2015 at 9:10 AM, Martin Magdinier <martin.m...@gmail.com> wrote:

Should we take this as an opportunity to finish the branding change? The only things left is renaming Google Refine Expression Language to General Refine Expression Language. 

That's a small enough change to put in easily.  I've put up a survey form to collect votes from the community on a new name.

I'm also thinking about either changing Jython to Python or making it something like Python (Jython) to make it more recognizable.  I forgot to include that in my email, but will add it as a postscript.  What do folks here think?

Tom

[Thad Guidry]

I'm also thinking about either changing Jython to Python or making it something like Python (Jython) to make it more recognizable.  I forgot to include that in my email, but will add it as a postscript.  What do folks here think?

​

Think about a change of Jython to instead have a label of Python as an expression language in the editor dialog to make it easier for folks to understand ?

Sure. +1

Thad

+ThadGuidry​

 

[Tom Morris]

Has anyone been able to do any testing on 2.6-rc1?  On what platforms?

I'm going to add another bug to the Must Fix list because Google just turned off the API that we were using to create Google Spreadsheets uploads:

https://developers.google.com/google-apps/documents-list/

https://github.com/OpenRefine/OpenRefine/issues/996

Tom

[Thad Guidry]

My quick cursory pass with a few tests in various areas on Win7 64bit with Chrome latest:

Expression Editor: OK

Sorts: OK

Records handling: OK

Import/Export with Templates: OK

Project Saves, Creates: OK

Column handling: OK

Faceting/Operations: OK

Undo/Redo: OK

I think it looks fine actually for shipping.

Thad

+ThadGuidry

[Martin Magdinier]

I've been using it on ubuntu 14.04 + firefox since the release of 2.6 RC1 and reported all the issues.
Looks fine for the next steps.


Qi should also be able to comment on the RC1

Martin

[qi cui]

I tested on the same platform as Thad. Looks fine for me.

Plus, I have 2 PR in the queue for the 2.6 milestone:

PR #1000 for issue #540 to skip the empty URL when submit the import form 

PR #993 for issue #476 Sort command allows multiple instances to be run

If you have time, you can review/merge them and close the tickets. 

There's some imported issues which are quite old. Some of them may be are not valid any more, we can also consider to close it or update it. such as:

 Issue #486 Character encoding not being set in new projects

Issue #400  Numeric facets not being refreshed after Undo/Redo 

[Tom Morris]

Thanks for the feedback everyone.  Perhaps I'll ping the general list to see if I can scare up a Mac user or two as well as any others who'd like to be alpha testers.

Qi - I'm working my way through the PRs and will definitely get to yours before release.

All - There's not question that there are obsolete, invalid, miss-categorized issues -- not just the old one's pointed out by Qi.  All help in verifying, triaging, prioritizing, etc is gratefully accepted.

In addition to a final pass through the PRs and open issues, the other big thing on my list is to figure out the migration strategy for notifying Google Refine 2.5 users via the auto-update mechanism on the old site and directing them to download from the new site (as well as the hosting for new auto-update mechanism).

Any other loose ends that people know of?

Tom

Tom 

[Thad Guidry]

Yeah, we need to pay you for doing most of the work!  Redirect BountySource funds perhaps ?

Thad

+ThadGuidry

[Martin Magdinier]

Tom

Do you plan to have a RC2 to review the latest pull request submitted / merged?
How many RC should we planned before the final release?

Thanks for your help on this.

Martin

[Tom Morris]

I plan to create at least one more release candidate and ask for additional testers on the main Refine list.

I'm at Google I/O this week and at the Open Data Science Conference over the weekend (anyone else going?), so won't happen until next week.

Tom