Re: [Mayan EDMS: 2445] Re: Mayan EDMS version 3.0 beta 1 available for testing

[Roberto Rosario]

We've been improving the continious integration setup to generate
development Docker images alongside the automatic python testing. We just
need to add code to test these automatic Docker images too and they will be
ready for download.

On Sun, May 6, 2018, 5:40 PM Raul  wrote:

> I would also be interested in a docker image for testing.
> Will there be one?
>
> Am Samstag, 28. April 2018 00:51:58 UTC+2 schrieb David Kornahrens:
>>
>> Hello Roberto --
>> Glad to see you back around.
>>
>> I'm interested in testing out too.  Could you create a Docker upgrade for
>> this, as that is how I'm deployed with Django Storages for offloading files.
>>
>> Thanks,
>> David
>>
>>
>>
>> On Tuesday, April 10, 2018 at 9:21:03 PM UTC-4, Roberto Rosario wrote:
>>>
>>> This version is meant for users experienced with Mayan EDMS. Please do
>>> not in production. The purpose of this release is get feedback on all the
>>> changes and testing and bugs reporting. If want to test against real data,
>>> please make a separate copy of your documents and database first and use
>>> this copy for testing.
>>>
>>> Almost all the changes of Mayan EDMS NG 2.8 and Mayan EDMS NG 3.0 have
>>> been merged.
>>>
>>> The release notes summary is as follows:
>>>
>>>
>>>- Turning Mayan EDMS into a single page app. Views are rendered
>>>using partial templates. On the first render a root template containing 
>>> the
>>>menus, JavaScript and stying is sent to the browser. On subsequent usage
>>>only the area below the menu is refreshed. This results is a big speed
>>>boost and much less bandwidth consumption.
>>>- Project moved to Django 1.11.
>>>- Event notification. It is possible to subscribe to an event type
>>>for the entire system or to the event type of a specific document. If any
>>>of these subscribed events occur an entry will be added to the 
>>> notification
>>>menu entry. The default for this menu entry is to display a bell icon 
>>> and a
>>>badge with the number of unread notifications.
>>>- All the Python dependencies have been upgraded to their latest
>>>version.
>>>- The logic for searching documents is now different. Before, all
>>>the documents that matched at least one of the search terms were 
>>> returned.
>>>Now only the documents that match all the terms are returned. This is in
>>>essence an "AND" style logic. To allow the previous behavior, the "OR"
>>>search syntax was added. The syntax must be added in uppercase and 
>>> between
>>>the optional terms.
>>>- Normally the resolution for the display modes of documents was
>>>specified as a string containing the width and height concatenated with 
>>> the
>>>character 'x'. The display resolution settings have been separated into
>>>distinctive width and height settings. Instead of 
>>> DOCUMENTS_THUMBNAIL_SIZE,
>>>the settings are now DOCUMENTS_THUMBNAIL_WIDTH and
>>>DOCUMENTS_THUMBNAIL_HEIGHT. The same applies to the preview, display and
>>>print resolutions.
>>>- The upload wizard now features dynamic steps. The steps are
>>>defined by a new class called WizardStep. This allows integrators to
>>>customize the upload wizard to add their own steps without having to 
>>> modify
>>>the core code. This change also add the capability of disabling existing
>>>wizard steps form third party apps without having to make core code
>>>modifications.
>>>- A new default step was added to the upload wizard to specify the
>>>cabinets of new documents.
>>>- The code that detect the automatic orientation of PDF has been
>>>disabled by default. It can be enabled via the
>>>DOCUMENTS_FIX_ORIENTATION=True setting.
>>>- A new proposal system has been added via the Mayan EDMS Request
>>>for Comment (or MERC for short) documents. The first two MERCs have been
>>>approved. MERC-1 which documents the process itself and MERC-2 which
>>>documents how API tests are to be written. Other MERCs are in review
>>>process.
>>>- If the duplicates of a document were deleted the original document
>>>would still show up in the duplicated document list with a duplicate 
>>> count
>>>of 0. This has been fixed.
>>>- Support was added to pass arguments to the storage drivers. This
>>>removes the need to subclass a storage driver to change its behavior. 
>>> This
>>>also means that passing global variables via the  local.py file to use S3
>>>style object storages is no longer required. These storage drivers can be
>>>configure by passing their arguments in the new
>>>DOCUMENTS_STORAGE_BACKEND_ARGUMENTS as a YAML string.
>>>- If is possible to list only the system events executed by one
>>>user. This can be accomplished via the user list view in the setup menu. 
>>> Or
>>>by clicking on the user name of the event list view.
>>>- The checkbox behavior in all the views that 

[Mayan EDMS: 2445] Re: Mayan EDMS version 3.0 beta 1 available for testing

[Raul]

I would also be interested in a docker image for testing.
Will there be one?

Am Samstag, 28. April 2018 00:51:58 UTC+2 schrieb David Kornahrens:
>
> Hello Roberto --
> Glad to see you back around.
>
> I'm interested in testing out too.  Could you create a Docker upgrade for 
> this, as that is how I'm deployed with Django Storages for offloading files.
>
> Thanks,
> David
>
>
>
> On Tuesday, April 10, 2018 at 9:21:03 PM UTC-4, Roberto Rosario wrote:
>>
>> This version is meant for users experienced with Mayan EDMS. Please do 
>> not in production. The purpose of this release is get feedback on all the 
>> changes and testing and bugs reporting. If want to test against real data, 
>> please make a separate copy of your documents and database first and use 
>> this copy for testing.
>>
>> Almost all the changes of Mayan EDMS NG 2.8 and Mayan EDMS NG 3.0 have 
>> been merged.
>>
>> The release notes summary is as follows:
>>
>>
>>- Turning Mayan EDMS into a single page app. Views are rendered using 
>>partial templates. On the first render a root template containing the 
>>menus, JavaScript and stying is sent to the browser. On subsequent usage 
>>only the area below the menu is refreshed. This results is a big speed 
>>boost and much less bandwidth consumption.
>>- Project moved to Django 1.11.
>>- Event notification. It is possible to subscribe to an event type 
>>for the entire system or to the event type of a specific document. If any 
>>of these subscribed events occur an entry will be added to the 
>> notification 
>>menu entry. The default for this menu entry is to display a bell icon and 
>> a 
>>badge with the number of unread notifications.
>>- All the Python dependencies have been upgraded to their latest 
>>version.
>>- The logic for searching documents is now different. Before, all the 
>>documents that matched at least one of the search terms were returned. 
>> Now 
>>only the documents that match all the terms are returned. This is in 
>>essence an "AND" style logic. To allow the previous behavior, the "OR" 
>>search syntax was added. The syntax must be added in uppercase and 
>> between 
>>the optional terms.
>>- Normally the resolution for the display modes of documents was 
>>specified as a string containing the width and height concatenated with 
>> the 
>>character 'x'. The display resolution settings have been separated into 
>>distinctive width and height settings. Instead of 
>> DOCUMENTS_THUMBNAIL_SIZE, 
>>the settings are now DOCUMENTS_THUMBNAIL_WIDTH and 
>>DOCUMENTS_THUMBNAIL_HEIGHT. The same applies to the preview, display and 
>>print resolutions.
>>- The upload wizard now features dynamic steps. The steps are defined 
>>by a new class called WizardStep. This allows integrators to customize 
>> the 
>>upload wizard to add their own steps without having to modify the core 
>>code. This change also add the capability of disabling existing wizard 
>>steps form third party apps without having to make core code 
>> modifications.
>>- A new default step was added to the upload wizard to specify the 
>>cabinets of new documents.
>>- The code that detect the automatic orientation of PDF has been 
>>disabled by default. It can be enabled via the 
>>DOCUMENTS_FIX_ORIENTATION=True setting.
>>- A new proposal system has been added via the Mayan EDMS Request for 
>>Comment (or MERC for short) documents. The first two MERCs have been 
>>approved. MERC-1 which documents the process itself and MERC-2 which 
>>documents how API tests are to be written. Other MERCs are in review 
>>process.
>>- If the duplicates of a document were deleted the original document 
>>would still show up in the duplicated document list with a duplicate 
>> count 
>>of 0. This has been fixed.
>>- Support was added to pass arguments to the storage drivers. This 
>>removes the need to subclass a storage driver to change its behavior. 
>> This 
>>also means that passing global variables via the  local.py file to use S3 
>>style object storages is no longer required. These storage drivers can be 
>>configure by passing their arguments in the new 
>>DOCUMENTS_STORAGE_BACKEND_ARGUMENTS as a YAML string.
>>- If is possible to list only the system events executed by one user. 
>>This can be accomplished via the user list view in the setup menu. Or by 
>>clicking on the user name of the event list view.
>>- The checkbox behavior in all the views that display a list items 
>>has been improved. A "check all" checkbox was added that will auto select 
>>all items. The submit button from dropdown list of actions was removed. 
>>Instead the action of selecting an item from the action dropdown will 
>>trigger the action. The checkbox also allow block selection. Clicking on 
>>the checkbox of the first