| Summary: | New release with fixes from osnola needed | ||
|---|---|---|---|
| Product: | Document Liberation Project | Reporter: | Mike Kaganski <mikekaganski> |
| Component: | libetonyek | Assignee: | Not Assigned <libreoffice-bugs> |
| Status: | NEW --- | ||
| Severity: | normal | CC: | alonso, aron.budea, dtardon, stephane.guillou |
| Priority: | medium | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | All | ||
| See Also: | https://bugs.documentfoundation.org/show_bug.cgi?id=140541 | ||
| Whiteboard: | |||
| Crash report or crash signature: | Regression By: | ||
| Bug Depends on: | |||
| Bug Blocks: | 124107 | ||
|
Description
Mike Kaganski
2022-08-19 09:57:03 UTC
Let's ask for Alonso's and David's take. Normally, it is rather David who takes care of creating a new release. For me, it's tricky, because I lack some rights: - I'm not admin for libetonyek on coverity, so I can't ask him to test a new version ; the last checked version is from 16/may/2021, - I don't think I have the rights to add files on https://dev-www.libreoffice.org/src/libetonyek/ and if I'm not mistaken, it's a necessary step. Agree it would be good to tag a new version in order to get the fixes into LO, marking as "new". @David, do you think you could prepare a new libetonyek release? |