-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Jean-François Lamy
committed
Sep 22, 2024
1 parent
e130fd8
commit 45117da
Showing
9 changed files
with
40 additions
and
86 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,50 +1,30 @@ | ||
| > [!IMPORTANT] | ||
| > [!WARNING] | ||
| > | ||
| > - You should test all releases, with actual data, *several days* before a competition. | ||
| > - It is always wise to export your current database before updating if it contains important data. | ||
| > - This is a release candidate [(see definition)](https://en.wikipedia.org/wiki/Software_release_life_cycle#Release_candidate), used for final public testing and translation. *It is still a preliminary release* | ||
| > - You should test all releases, with actual data, *several days* before a competition. This is especially important when considering the use of a release candidate. | ||
| - Maintenance log | ||
| - Maintenance log: | ||
| - rc02: fix issue with liftType published during event forwarding to public results and video information feeds. | ||
| - rc01: Translations for de, dk, ro, hu, pt, fr | ||
| - beta04: Fixed an empty cell in the translation file that was preventing languages from being loaded. | ||
| - beta03: Fixed the propagation of the selected Best Athlete scoring system to the classes that need to know (e.g. Athlete) | ||
| - beta02: Changed the standard final package templates to use the selected Best Athlete scoring system | ||
| - beta02: Updated the Result Documents documentation. | ||
| - beta01: Jury sheets no longer have a forced page break. Scoring sheet in a second tab. | ||
| - beta01: Updated translations to use Q-Youth and Q-Masters for the Huebner age+bodyweight scaled totals. | ||
| - Ability to override the Best Athlete scoring system | ||
| - On the competition results page, it is possible to select a scoring system that will be shown in the grid. This allows computing the best athlete for a championship using a different scoring system (for example, using Q-youth age-adjusted totals for a Youth Championship) | ||
| - The standard templates have been updated to use the Best Athlete scoring system selected if one is picked (the default is the competition global best athlete scoring system) | ||
| - Children Categories Bar Rules | ||
| - The feature flag `lightBarU13` selects using the 15kg bar for boys in the U11 and U13 categories. This is the same as removing the 20kg bar for younger boys age groups. However, if an athlete needs the 20kg bar, the "Non-Standard bar" feature can be used. | ||
| - Support for Q-masters results | ||
| - Q-masters is like SM(H)F but based on Q-points instead of Sinclair. It is Q-points * the same age factor as SM(H)F | ||
| - The default templates for Masters protocols, result sheets and competition books now show the Q-masters value in addition to the SM(H)F. | ||
| - Import of External Session Results: the following is now possible | ||
| - If a session needs to be run outside or in another building a) perform weigh-in normally and enter data normally in the main database. b) Export the main database and load it into the owlcms running in the other building c) Run the session, export the remote database c) Use the new feature at the bottom of the Results page to selectively read back the lifts from the remote session. | ||
| - Only the lift information is read back. Note that owlcms follows the rules and will determine winners according to the lifting order that would have been followed had all sessions taken place normally. | ||
| - jxls3 Templates | ||
| - In the top cell, where `jx:area` is given, it is now possible to add a directive of the form `owlcms:fixMerges(4, [1, 2, 3])` This would merge cells vertically in columns 1, 2, 3, starting with row 4. The cells are merged from the non-empty value down to the next non-empty cell. This is a workaround for a limitation/bug in jxls3. See the `templates/schedule/DaySchedule.xlsx` file for an example. | ||
| - Locale: fixed a race condition where pages would load before it was determined that the application should switch to English because there is no translation for the local language. | ||
|
|
||
| - 52.0.6 | ||
| - Weigh-ins and registrations | ||
| - When weight is cleared and category is defined, don't reset eligibilities needlessly | ||
| - When a super-heavyweight athlete from a youth age group weighs in, correctly recompute the participation in older age groups if eligible. | ||
| - Record Exports. Fix: The file produced by an export records definition could not be read back as is. | ||
| - Break Timers: if a short CJ break was running, it was not cancelled if a longer break was started manually | ||
| - Medal Schedule: Added a new template that lists, for each category, when the medals will be handed out (computes when the last athlete from that category is done) | ||
| - 52.0.5 | ||
| - Publicresults: improved traces and exception catching for cleaner logs. | ||
| - Competition Results: | ||
| - Recalculate Ranks now recomputes the global best lifter ranking according to the selected global scoring system | ||
| - The championship category names are now used when producing the result sheet for a specific championship. Each athlete appears once under the most specific category he is registered in that championship. | ||
| - Updated the Scores templates. This is used when Age-Group-Specific scores are used. Now shows the global "Best Lifter" scores as well. | ||
| - 52.0.4 | ||
| - Fix: If "Medals according to score" or "Show Score on Scoreboard" are selected, then the global Scoring System is displayed on the scoreboard (as was the case in previous release) | ||
| - (Advanced usage note) If an AgeGroup-specific scoring system has been defined using the AgeGroups file, then the score and rank columns are automatically shown for any session in which such an age group is present, and the specific rankings are used instead of the global one. | ||
| - Translations (ru) | ||
| - 52.0.3 | ||
| - Publicresults: fixed memory allocation configuration for using large containers in large competitions (ex: 200 simultaneous viewers of scoreboards for 3 simultaneous platforms) | ||
| - owlcms: fixed occasional extra notification of weight changes to the announcer. | ||
| - owlcms: ${athlete.categoryFinished} can now be used in results templates (those used in the Session Results page). When producing interim results, this variable can be used to hide athlete ranks in categories where some athletes have finished but others still need to lift. | ||
| - 52.0.2 The new faster SBDE (Start Book Data Entry) full export was not correctly exporting the session information, now fixed. | ||
| - 52.0.2 Fixed formatting for schedules, restored the DaySchedule with individual age groups. | ||
| - 52.0.1 Overzealous check was preventing some customized schedules from printing. | ||
| - **MIGRATION NOTES** | ||
| - If you have created your own document templates, or if you created a "kit" of local documents for your federation, some templates have been moved to more specific folders and you may need to move your own templates. Install a clean copy of the application and look at the locations in `local/templates`. Use the updated `Prepare Competition > Documents` page to check that the buttons show your templates. | ||
| - Documents: New and Improved Documents page | ||
| - All documents needed to prepare and run the competition are here (Results are still on their own page). | ||
| - The Competition-wide documents such as the Start List are handled as in the previous versions. | ||
| - Documents like the Athlete Cards can be produced for one or more sessions. If more than one session is selected, a zip file is produced, otherwise the Excel is produced. | ||
| - Document sets can be produced, for example, a weigh-in form together with the cards. When a document set is selected, a zip file is produced. The document set can be produced for one or more sessions. | ||
| - If more than one copy of a document is needed (for example, two weigh-in forms for each session), you can adjust your template by duplicating the tab. Same for jury forms if you want to avoid printing 3 copies manually. | ||
| - Schedule: | ||
| - added a Simple schedule template that uses the description of the sessions. | ||
| - A more sophisticated DaySchedule template shows age groups and bodyweight categories, now available in local languages. | ||
| - Scoreboards: | ||
| - Fix: Immediately after the 3rd snatch, while the decision lights were shown, the bottom line of the scoreboard would be stretched. Now fixed. | ||
| - SBDE export: | ||
| - Converted the template to jxls3, resulting in massive speed improvement (~7 seconds for 1000 athletes). | ||
|
|
||
|
|
||
|
|
||
| For other recent changes, see [version 50 release notes](https://github.com/owlcms/owlcms4/releases/tag/50.0.0) and [version 51 release notes](https://github.com/owlcms/owlcms4/releases/tag/51.0.0-rc02) | ||
| For other recent changes, see [version 51 release notes](https://github.com/owlcms/owlcms4/releases/tag/50.0.0) and [version 52 release notes](https://github.com/owlcms/owlcms4/releases/tag/52.0.6) |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.