In the current code base, choosing to run public or public-new interface is a build option. Is the plan for the release to bundle both for side-by-side testing and evaluation, and allow turning one off in the config file, or will this still be a custom build option ?
( I’m suggesting the former, BTW, but wondering what others preference is. ) — Steve Majewski On Mar 6, 2017, at 12:21 PM, Christine Di Bella <[email protected]<mailto:[email protected]>> wrote: The next release of ArchivesSpace will reflect significant improvements in the underlying technology for the application, including upgrades to Rails 5 and JRuby 9.1.x. It will also feature the beta of the new public interface. To reflect the significance of these changes, the next version will be numbered 2.0.0. If you are looking ahead and thinking about IT resources needed for the 2.0.0 upgrade, please keep in mind that these changes will affect plugins and some local modifications. We’ll provide more guidance about how to adapt your plugins and modifications as we get closer to the final release. Also, this upgrade will require a complete re-index of your database. More information about 2.0.0 will be shared as the month progresses and we will be holding a webinar close to the time of the release that highlights the changes from a user and technological standpoint.
_______________________________________________ Archivesspace_Users_Group mailing list [email protected] http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
