Releasing 3.6.0

10 views
Skip to first unread message

Antonin Delpeuch (lists)

unread,
Jul 18, 2022, 4:28:58 PMJul 18
to openref...@googlegroups.com
Hello all,

Since I have not seen reports of problems specific to 3.6-rc1, I propose
to turn it into a 3.6.0.

Thoughts?

Antonin

Isao Matsunami

unread,
Jul 18, 2022, 4:45:19 PMJul 18
to openref...@googlegroups.com
Merci pour votre devotion, Antonin
I’m very looking forward to 3.6


2022年7月19日(火) 5:28 Antonin Delpeuch (lists) <li...@antonin.delpeuch.eu>:
--
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/openrefine-dev/2fa0ff75-9604-1bd5-c1a6-3c999c9f2c7a%40antonin.delpeuch.eu.
--
*************************************************
中日新聞電子編集部
松波 功 Isao Matsunami

451-0043 名古屋市西区新道1-2-18-908
mobile: +81-90-3954-5786
mail: isa...@on.rim.or.jp  PGP:1DF1 4682
*************************************************

ow...@ostephens.com

unread,
Jul 19, 2022, 4:18:42 AMJul 19
to OpenRefine Development
Sounds good to me

Thanks Antonin

Antoine Beaubien

unread,
Jul 19, 2022, 10:32:05 PMJul 19
to OpenRefine Development
Antonin,

   I just wanted to say that I have projects that open in v3.6rc1 and not in v3.5.2. Nor sure if backward compatibility at the workspace level is important, but I see some projects that can't open back. Haven't tried the Import/Export project.

Regards,
   Antoine

Antonin Delpeuch (lists)

unread,
Jul 20, 2022, 4:27:24 AMJul 20
to openref...@googlegroups.com

Hi Antoine,

Thanks for the reminder. Yes I can reproduce your issue: this must be linked to the new format for Wikibase schemas or manifests.

I think that is called "forward compatibility" (unless it is the other way around?) and we have not been enforcing that so far. It is harder to enforce than backwards compatibility.

We can think about how to support that better, but I think it should not be a blocker for 3.6.0.

Best,

Antonin

--
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.

Antoine Beaubien

unread,
Jul 23, 2022, 5:34:19 PMJul 23
to OpenRefine Development

Hi Antonin,

> I think that is called "forward compatibility" (unless it is the other way around?)

Hum. From what I understand, being able to open a v3.5 file in v3.6 is forward compatibility, and that is expected of most softwares, and we do it. 

https://en.wikipedia.org/wiki/Backward_compatibility

> and we have not been enforcing that so far. 

I've never seen here a strong commitement to backward compatibility, nor do I think a lot of users would need it, unless they must use an extension that is not working with the latest release.

> It is harder to enforce than backwards compatibility.

Yes, but a version v3.5.3 would probably be easier. But is it worth the work? I don't know.

Regards,
   Antoine

Reply all
Reply to author
Forward
0 new messages