Thanks for the update, Cyrus. Does this mean we could upgrade directly from 
v3 to v4.4.2 without going first to v4.4.1?

Regards,

Joel


On Saturday, June 29, 2019 at 2:36:04 AM UTC+8, Cyrus Hiatt wrote:
>
> The Arches team is happy to announce the 4.4.2 release which includes a 
> number performance improvements and bug fixes:
>
> Here some of the release highlights:
>
>    - Fixes issue preventing Resource editors from editing without being 
>    members of the Graph Editor group
>    - Improves error logging particularly for collector sync transactions
>    - Fixes top margin of the default report
>    - Fixes bug preventing app from loading without the DEFAULT_BOUNDS 
>    defined
>    - Deletes uploaded files when their respective tiles are deleted
>    - Improves v3 to v4 migration process
>    - Adds support for jsonl, multiprocessing data load
>    - Allows setup_db to be executed without superuser permissions
>    - You can find the detailed release notes here: 4.4.2 release notes 
>    
> <https://github.com/archesproject/arches/blob/stable/4.4.2/releases/4.4.2.md>
>
> Users are encouraged to update at their earliest convenience. If you are 
> upgrading from Arches 4.3, be sure to follow the project upgrade 
> instructions to 4.4.1 
> <https://github.com/archesproject/arches/blob/stable/4.4.x/releases/4.4.1.md> 
> before proceeding.
>
> As always the documentation can be found at <http://arches.readthedocs.io>
>

-- 
-- To post, send email to archesproject@googlegroups.com. To unsubscribe, send 
email to archesproject+unsubscr...@googlegroups.com. For more information, 
visit https://groups.google.com/d/forum/archesproject?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"Arches Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to archesproject+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/archesproject/5786eee6-cb14-49f7-9597-6c4de8e2968e%40googlegroups.com.

Reply via email to