Nicolas Vengeon authored 2 years ago and Sébastien Blin committed 2 years ago

- Standard time/date is now used
- If today, show local time, otherwise show local date

GitLab: #545
Change-Id: I07f1e706868c725d1c917c473dc0fdbad8d6810f

Nicolas Vengeon authored 2 years ago and Sébastien Blin committed 2 years ago

- Contributor added to credits

Change-Id: I27d459557c10e50c53b342472ed76c2c7966ff37

Amin Bandali authored 2 years ago and Sébastien Blin committed 2 years ago

* extras/packaging/gnu-linux/scripts/release-version.sh: Add script
for deriving (reproducibly) a release version.  The format will follow
a 'YYYYMMDD.X' scheme, where 'YYYYMMDD' is the date of the last commit
on the current branch, and 'X' the number of releases tagged that day,
starting from zero.  Example: the first stable release with a newest
commit date of 2023-01-02 would have a version of '20230102.0', the
subsequent one '20230102.1', and so on.  This is derived by counting
the number of git tags with the prefix 'TYPE/YYYYMMDD', where 'TYPE'
is the release type: either 'stable', 'beta', or 'nightly'.
* extras/packaging/gnu-linux/Jenkinsfile: Call the above new script to
derive the release version to use for tagging.
* extras/packaging/gnu-linux/Makefile: Switch from the previous
'jami_YYYYMMDD.hhmm.COMMIT.tar.gz' tarball filename format to
'jami-YYYYMMDD.X.tar.gz'.  The new format is shorter, omits the
unnecessary and confusing commit id, and uses dash instead of
underscore.  Also, it contains everything in a top-level directory
with the same name as the tarball (without the .tar.gz extensions),
so that 'jami-YYYYMMDD.X.tar.gz' nicely extracts to 'jami-YYYYMMDD.X'.
With these changes, our release tarballs will follow more closely the
related instructions from the GNU maintainers manual:
https://www.gnu.org/prep/maintain/html_node/Distribution-tar-Files.html
Lastly, this change inadvertently 'fixes' a recent issue where the
'extras/ci/client-qt-gnulinux' subdirectory and its contents would be
moved to top-level in the tarball due to one of the tarball transforms
matching the 'client-qt' in the directory's name, replacing the
'extras/ci/client-qt' prefix with 'client-qt', thereby resulting in
'client-qt-gnulinux' being moved to the tarball's top-level.
* .gitignore: Ignore several packaging-related directories and files.
* extras/packaging/gnu-linux/rules/rpm/jami-daemon.spec:
* extras/packaging/gnu-linux/rules/rpm/jami-libclient.spec:
* extras/packaging/gnu-linux/rules/rpm/jami-qt.spec:
* extras/packaging/gnu-linux/rules/rpm/jami.spec: Update the expected
release tarball filename pattern in the 'Source' field.  Also replace
references to previous top-level directory name 'client-qt' with the
new one 'jami-%{version}' where needed.
* extras/packaging/gnu-linux/rules/rpm/jami-libqt.spec: Update the
'Source' field to follow new tarball name consistent with the main
Jami release tarball.
* extras/packaging/gnu-linux/scripts/build-package-rpm.sh: Update the
tarball top-level directory pattern for the new format, now passing
the --wildcards option to GNU Tar.  Also use a name for the jami-libqt
source tarball that is more consistent with the main Jami release
tarball.
* extras/packaging/gnu-linux/scripts/build-package-snap.sh: Update the
top-level directory pattern for the new format.
* extras/packaging/gnu-linux/tarballs.manifest: Drop file accidentally
checked into git.

Change-Id: I2695f560c0bc5e61fb99dc0244f8fbb8e7026a62

Change-Id: Ib11d464284effa5e78ca56441d0e535858071151
GitLab: #941

Because in a swarm you can talk with non contacts, we should at
least retrieve the username when possible.

Change-Id: Ie01cd10cc1231fc4024bd5a08c30c08d69e8e7f0
GitLab: #948

Change-Id: I9eb8843d50fdeb914eae622c15555b366d246094

Nicolas Vengeon authored 2 years ago and Andreas Traczyk committed 2 years ago

SFPM performs poorly compared to its C++ counterpart in cases where re-filtering often is required. Tests show SFPM taking roughly 10x that of QSFPM in certain cases when the entire conversation needs to be loaded.

Change-Id: I25792f0ab376ae11d42073a548934b743e59fa3e

Change-Id: I6c36ab045667d01859a72dfec12e3e02130c57fe
GitLab: #947

Nicolas Vengeon authored 2 years ago and Sébastien Blin committed 2 years ago

Change-Id: I6ef8069de9012e235fe6f8907b9d2bb94a44cd40
GitLab: #634

Change-Id: I3501d0ba072bc68685af8ba8c46c22979cc25493

Change-Id: I3fcb60aed90e3a7cf7edee7f8ac28c204dbb8952

So that users can know when a message is deleted and can check
previous version like any edited version.

Change-Id: If3c1daeec930bd4b0f359573b971790199397489

Aline Gondim Santos authored 2 years ago and Andreas Traczyk committed 2 years ago

Change-Id: Ie1708ae4be049206fb8337db1211b7844e45726f

Nicolas Vengeon authored 2 years ago and Sébastien Blin committed 2 years ago

Change-Id: I790f10542aed306a7416a4ce79f2eaf7a770135a
Gitlab: #698

This patch sets up app updates to use EdDSA signature as now
it is required by Sparkle

Change-Id: I68a581e21850f04a819f4fe7ea49a33766031e01

Nicolas Vengeon authored 2 years ago and Sébastien Blin committed 2 years ago

Change-Id: Ica33126a1d75b4880c70c1e7f654f82db6499bbd

Scenario, create a swarm with self.
As a warning, it will show "Can't find contact YOUR_ID  this is a
bug, please report" because your account is not in your contacts.

Change-Id: I6f49f8fa77132daf00396b62da9ded470df49f98

Else, the text was overflowing

Change-Id: Idd27682d612cc35fce045967025df49ad1a1a202

If a user join a conference with video enabled, but without any
valid camera and try to un-mute/mute in loop, it will add
new empty medias with incorrect sources causing duplicated participants
in the conference.

Change-Id: Ifa0dc090ca49ae6f9799f1209f3514cf540365da

This reverts commit ab8c3645.

Reason for revert: It breaks the sharing functionality in windows

Change-Id: Ia031bec6d82462115e3086ab9300b3aef99d9bab

Nicolas Vengeon authored 2 years ago and Sébastien Blin committed 2 years ago

GitLab: #634
Change-Id: I4c95622297e52d4b7fb5ea42426353a3b3579186

Andreas Traczyk authored 2 years ago and Sébastien Blin committed 2 years ago

Change-Id: If3ee1fd3f074e8807fedc66fc02758df62789b39

1. sourceParent and destinationParent were incorrect.
2. Moving always all the message can be incorrect if parentIdx >
msgIdx after a merge

Change-Id: I0ab8eeabb61926d5c0c22d8fed68c60d54178bf6
GitLab: #939

Change-Id: I7bd12dbc3bf512b3cd880892d2afda17c8117bd6
GitLab: #862

Jenkins authored 2 years ago and Sébastien Blin committed 2 years ago

Change-Id: I01e1a0f0b41387ce97a3800ed56dbdb3e839b912

This was broken when passing to only conversation's requests with
an un-needed condition

Change-Id: Ibe422474037c60ede21425b016017615d1bbf0f5

Change-Id: I6d10827c4b5dcd2cddc8516f3c30d3f986774ffb

On some cases (like many edition/reply) the atYBeginning is still true
causing the view to not load messages anymore (after retrying it loads
as the beginning)

Change-Id: I9da474224f6fc0a39cf405c8bfe9d5201849ea64

Change-Id: Ie775c846c69b7f364b24f8c0726c15044e18b985

Aline Gondim Santos authored 2 years ago and Adrien Béraud committed 2 years ago

If a window changes its name, we should share the parent process windows.
This can happen with chrome, visual studio code and file explorer for example.

+ Fixes non opening SelectScreen window when Jami language changes.

Change-Id: Ib16992dde08e6a9fa191c9fb1cbc4efd304efe6d

Kateryna Kostiuk authored 2 years ago and Kateryna Kostiuk committed 2 years ago

Change-Id: I0e0414b928dcf53158e35803878f9c587944d4ac

Nicolas Vengeon authored 2 years ago and Sébastien Blin committed 2 years ago

Change-Id: I7a6214e4b6f4219af1b1d731b4553975e3e311a1
GitLab: #931

Change-Id: I7ffe7e155cb76aff95113b2fe7215f86ee127252

Because docker mount extras/packaging/gnu-linux/packages:/opt/output
the Makefile MUST creates the directory for current user else
the resulting directory will use the Docker user (root), causing
the file to not be removed.

Change-Id: I91dadfa766730d163de4cf091bb1b9b8193f7d24

Nicolas Vengeon authored 2 years ago and Sébastien Blin committed 2 years ago

Change-Id: Ie04791adc2f914a2b12688488476aca8617ec0d3

Change-Id: Ic3328ea069af093d412abd7fea29a2df199c1052

+ moveMessage was doing useless computation to move messages one
by one even if blocks are supported
+ beginMoveRows/endMoveRows seems to do weird stuff if all the rows
should be moved causing some crashes. beginReset in this case
doesn't trigger this weird behaviour and is more efficient.

Change-Id: Ia4eb3cdbbe74bf9215fb673cb9af571f67225ffe

- added color to container

Change-Id: I95532aa0540dade358925cd0720aa8024807961f

Change-Id: I172139df931dbfaa7850387f5bdaf6d1bd6a0561

Change-Id: Ib31e7d311540d889283de681d74c1f8f82870365