Feature Wiki
Tabs
JourFixe-2018-09-10
Page Overview
[Hide]Date and place
Monday, September 10, 2018 from 13:00 – 16:40 at ILIAS-Verein office in Köln
Time | Topic |
---|---|
13:00 - 14:20 | 1. Appointments |
14:30 - 17:30 | 3. Developing 5.4 |
17:30 - 18:00 | 4. Miscellaneous |
Participants
At ILIAS office:
- Kunkel, Matthias [mkunkel] (Minutes), Killing, Alexander [alex], Jansen, Michael [mjansen], Seeland, Per Pascal [PerPascalSeeland], Famula, Thomas [tfamula], Zenzen, Enrico [ezenzen], Tödt, Alexandra [atoedt], Meyer, Stefan [smeyer]
- Schmid, Fabian [fschmid], Amstutz, Timon [amstutz], Glaubitz, Marko [mglaubitz], Klees, Richard [rklees], Heyser, Björn [bheyser], Seiler, Yvonne [yvseiler], Heer, Raphael [rheer], Samoila, Oliver [oliver.samoila]
If you like to participate at the Jour Fixe via Skype, please join our Skype meeting!
1 Appointments
- 19 SEP 2018, 09:00 - 16:00: "Workshop Workflow Engine" at University of Cologne | this is a introduction on how to use the Workflow Engine | main target group are developers | maximum number of participants is 8 | Please contact Klees, Richard [rklees] if you want to participate!
- 20 SEP 2018, 14:00 - 15:00: Workshop "HTML-Content in Media Objects - Subdomain-Isolation and RBAC-Solution" in Skype
- 21 SEP 2018, 10:00 - 12:00: "Workshop 'Assessment Question Service Concept'" in Skype
- 02 OCT 2018, 14:00 - 16:00: "Workshop 'Include a new generic Content-Style'" in Skype
If you want to participate at one of the above mentioned workshops, please register for the related session. This helps to organise the workshop. Thanks!
2 Maintained Versions
2.1 Roadmap
Last releases:
- ILIAS 5.3.8 published at August 29, 2018
- ILIAS 5.2.18 published at August 08, 2018
- ILIAS 5.1.28 published at August 01, 2018 – this is the last maintained release for 5.1!
- ILIAS 5.3.9 scheduled for September 2018
- ILIAS 5.2.19 scheduled for September 2018
2.2 Mantis Bug Reports
All open issues reported or modified since the last Jour Fixe were screened by the product manager before the Jour Fixe and assigned to the responsible developers if necessary. The following issues were discussed in detail:
- #23302 : Hover background in autocomplete : Please add the hand to all options even if they are not with a-tags.
- none
2.3 Bugfixing Statistic
Bug reports[1] set to status 'open' and not been touched by responsible maintainer for more than 21 days (checked this morning) as well as bug reports with priorisation voting:
Responsible Maintainer | Open bugs without feedback | Last JF | ø Age in days | Last JF | New Votes* | Old Votes** | Resolved*** |
---|---|---|---|---|---|---|---|
6 | 162 | 1x2v | |||||
4 | 3 | 47 | 42 | 1x1v | |||
11 | 38 | 25x1v | |||||
Thomas Joussen | 1 | 1 | 94 | 80 | |||
49 | 37 | 52 | 46 | 3x1v | 1x2v 4x1v | ||
1x1v | |||||||
2 | 14 | 117 | 100 | 2x1v | |||
4 | 6 | 276 | 183 | 1x1v | |||
10 | 9 | 132 | 144 | 1x1v | 1x4v 1x3v 2x2v 21x1v | ||
1 | 53 | ||||||
1x3v | |||||||
Benjamin Seglias | 1x1v | 2x2v | |||||
7 | 132 | 1x1v | |||||
1x1v |
* New votes: bugs priorised within the last 14 days ** Old votes: priorised bugs before last JF (older then 14 days) *** Resolved: Resolved or closed bug reports in the last 14 days
Bug reports with status 'Fixing according to priorisation' should be fixed before other bugs are tackled. Priorised bugs very important for one or more institutional members of the ILIAS society. Handling this reports with low priority contradicts the intention of the established bug fixing process.
2.4 Open Pull Requests to Discuss
The following pull requests in the ILIAS GitHub repository were marked with 'Jour Fixe' this morning:
- PR 1169 • Docs: Coordinator Update : We highly appreciate this suggestion but would like to have an addition to the rules to cover the problem of responsibilies in Mantis (or in other applications that do not allow more than one contact person):"* If two people share the role of the coordinator they MUST define whom of them is contact person for Mantis bug reports as well as for other applications that do not support more than one contact."
- none
2.5 Continuous Integration
Overview on current status and reports from CI-server at http://ci.ilias.de:
- automated tests: 3031 (+57) passing unit tests on PHP 7.0, PHP 7.1..
- skipped tests in WAC ("WIP")
- tests that depend on ilDB in WFE-tests -> ilDB throws notices, which PHPUnit finds suspicious
- tests using abstract classes in T&A
- results of dicto architectural tests
- 108 violations (net) fixed since JF 2018-08-27
- 1 violation added: ilLanguage contains a dependency to ilDB in the destructor. This started to throw errors during tests because it was switched to DIC. The problem was aleviated with DIC::isDependencyAvailable, but this is only supposed to be a temporal fix, thus flagged by the DIC.
- Please run unit tests locally before committing.
- Travis CI for ILIAS:
- https://travis-ci.com/ILIAS-eLearning/ILIAS/builds
- expanded to release_5-3-Branch: https://travis-ci.com/ILIAS-eLearning/ILIAS/branches
- more to come...
- Performance monitoring:
- Pascal is currently fixing the performance monitoring. No infos at the moment.
3 Developing 5.4
3.1 Release Cycle for Version 5.4
Feature freeze | 30 APR 2018 |
Coding completed | 29 OCT 2018 |
Test cases completed | 29 OCT 2018 |
Documentation of implementation completed | 29 OCT 2018 |
Beta1 release and start of testing 5.4 | 31 OCT 2018 |
Testing completed | 31 JAN 2019 |
End of bug fixing | 08 MAR 2019 |
Stable version 5.4.0 | 13 MAR 2019 |
In accordance with the Technical Board the product manager decided to set the documentation of implementation of a feature as another requirement to get an implemented feature into trunk. This information helps testers to understand the feature they have to test and improves the understanding of the feature for users. This requirement is effective from ILIAS version 5.4. Similar to test cases and approval, the documentation of implementation on the feature wiki page needs to be completed until October 29, 2018 for version 5.4.
3.2 Status of Development
Number of features scheduled for Release 5.4 and their status this morning:
Status | Today | Last JF | Diff |
---|---|---|---|
A - in trunk | 11 | 8 | +3 |
B - approved / committed soon | 0 | 0 | 0 |
C - waiting for approval | 13 | 10 | +3 |
D - in development | 6 | 7 | -1 |
E - contract settled | 32 | 20 | +12 |
F - option or agreement for funding | 35 | 52 | -17 |
G - partly funded | 0 | 0 | 0 |
H - funding needed | 13 | 14 | -1 |
Candidates for abandoned features | 2 | 2 | 0 |
Removed from code | 1 | 1 | 0 |
Notice: Features currently assigned to categories B to H have to be in the trunk until October 29, 2018 to become part of the official 5.4 release.
3.3 Development Issues in 5.4
- …
3.4 Feature Requests to be Discussed
The following features suggested for 5.4 were added to the data collection 'Suggestions for Jour Fixe Agenda' to be discussed today (see procedure documented in ILIAS community FAQ):
Page Layout Revision (Desktop) : We highly appreciate this suggestion and like it very much. The suggested layout revision goes into the right direction for us. We have the following comments:
- We would like to know how clicking through the tree could be possible without the need to present more than two indentations (left aligned + one). Matthias made a related suggestion. But there is also the need for opening more than one node at once to administer the course or category.
- We support the suggestion to always show the "Tools" menu item - even if only one tool is available at the moment. In our opinion this is easier to learn and helpful in case of support - except for the case when only one tool is offered at the installation (e.g. no help activated and only local navigation shown).
- We agree that the breadcrumb should only appear where it is already shown in ILIAS 5.
Page Layout Revision (Mobile) : We highly appreciate the current suggestions. Concerning Yvonne's question we decided:
- We follow Yvonne's suggestion and would like to have the top bar shown when opening the screen but changing to the reduced version with the top bar items behind the "vertical more" icon and the breadcrumb.
- We follow Yvonne's suggestion concerning the behaviour when clicking on a breadcrumb item. The breadcrump is closed and the called content shown.
- We prefer version 1 to handle the "Safari problem". This requires to double-click a menu item on Safari/iOS due to the iOS navigation bar.
Display Repository Root and Categories in Usage Intensity : We highly appreciate this suggestion and schedule the feature for 5.4.
Calendar Selection - Make link target clear : We discussed the suggestions but see a problem that we would introduce different behaviour when the link for course and group calendars open the course/group while the link for personal appointments, booking reservations or consultation hours are directed to sub-parts of the calendar. We discussed if the link for a course or group calendar should direct to the course/group calendar itself but have no clear idea what happens with the manage screen for this calendar and how to handle the Back-click-ways. It would be great if the suggestion could give an answer to these questions.
Remove the functionality to open collections in a Browser over WebDAV : We highly appreciate this suggestion and abandon the functionality to open collections in a Browser over WebDAV with 5.4. In case of entering a webdav link to the browser a re-direct should be made to the mount instructions for this repository node.
4 Miscellaneous
Support of Feature Workshops
- A new group Feature Workshops has been created at https://www.ilias.de/docu/goto_docu_grp_6768.html.
- Group is accessible for everybody with an account at ilias.de.
- Every workshop is represented by a session and can have an Etherpad or any other ILIAS tool to support the workshop.
- Group members get a calendar entry for all workshop dates.
- Development projects with a lot of workshops (like Page Layout Revision) can have separate groups.
- Entries in 'Appointments' list of JF agenda should link to session (a no longer to DC entry).
SOAP Testing for ILIAS 5.4 (Kruse, Fabian [Fabian])
- There has been some confusion about the testing of SOAP in the past few years.
- Attempts were made to test SOAP as a part of our community testing, using test cases in TestRail. But JF decided to reject the test cases, prefering an automated solution.
- As the test manager, I would like to know whether the SOAP test suite can be discarded and who - if anybody? - will take care of the automated tests.
JourFixe, ILIAS [jourfixe] : We do not want manual testing of the SOAP interface but prefer an automatic procedure. Facing the upcoming Service Discovery, we postpone testing of SOAP for 5.4 and hope we can solve this problem with the Service Disco. Test cases in Testrail can be removed.
Next Jour Fixe dates
- Monday, September 24, 2018, 13:00 - 18:00
- Monday, October 08, 2018, 13:00 - 18:00
Last edited: 19. Apr 2023, 12:28, Kunkel, Matthias [mkunkel]