[Libreoffice-commits] core.git: Changes to 'libreoffice-7-3-7'

2022-10-13 Thread Christian Lohmaier (via logerrit)
New branch 'libreoffice-7-3-7' available with the following commits:
commit d4dc78ab675aba3edd75b7f04afcceb9ab1b8a95
Author: Christian Lohmaier 
Date:   Thu Oct 13 12:48:27 2022 +0200

Branch libreoffice-7-3-7

This is 'libreoffice-7-3-7' - the stable branch for the 7.3.7 release.
Only very safe changes, reviewed by three people are allowed.

If you want to commit more complicated fix for the next 7.3.x release,
please use the 'libreoffice-7-3' branch.

If you want to build something cool, unstable, and risky, use master.



[Libreoffice-commits] core.git: Changes to 'libreoffice-7-3-6'

2022-08-18 Thread Christian Lohmaier (via logerrit)
New branch 'libreoffice-7-3-6' available with the following commits:
commit 8e6f5da042f08a80850581f9dc21989f8210463d
Author: Christian Lohmaier 
Date:   Thu Aug 18 19:35:39 2022 +0200

Branch libreoffice-7-3-6

This is 'libreoffice-7-3-6' - the stable branch for the 7.3.6 release.
Only very safe changes, reviewed by three people are allowed.

If you want to commit more complicated fix for the next 7.3.x release,
please use the 'libreoffice-7-3' branch.

If you want to build something cool, unstable, and risky, use master.

commit ad8bf9aa247c9afc69e002d14b23954254578bbe
Author: Christian Lohmaier 
Date:   Thu Aug 18 19:34:23 2022 +0200

Update git submodules

* Update translations from branch 'libreoffice-7-3'
  to 0c76c3acc2f3a417de5ef807ec23af245e75707b
  - update translations for 7.3.6 rc1

and force-fix errors using pocheck

Change-Id: I9ea0ea551d4cc2a4c1d6ddfe44f5bcf837b965f0



[Libreoffice-commits] core.git: Changes to 'libreoffice-7-3-5'

2022-07-01 Thread Christian Lohmaier (via logerrit)
New branch 'libreoffice-7-3-5' available with the following commits:
commit d7427a86b53e152553870355bf863de14c4479a4
Author: Christian Lohmaier 
Date:   Fri Jul 1 21:37:57 2022 +0200

Branch libreoffice-7-3-5

This is 'libreoffice-7-3-5' - the stable branch for the 7.3.5 release.
Only very safe changes, reviewed by three people are allowed.

If you want to commit more complicated fix for the next 7.3.x release,
please use the 'libreoffice-7-3' branch.

If you want to build something cool, unstable, and risky, use master.



[Libreoffice-commits] core.git: Changes to 'libreoffice-7-3-4'

2022-05-18 Thread Christian Lohmaier (via logerrit)
New branch 'libreoffice-7-3-4' available with the following commits:
commit f950f6fce23f03332ea394a6aaf23723c459d4fb
Author: Christian Lohmaier 
Date:   Wed May 18 19:50:10 2022 +0200

Branch libreoffice-7-3-4

This is 'libreoffice-7-3-4' - the stable branch for the 7.3.4 release.
Only very safe changes, reviewed by three people are allowed.

If you want to commit more complicated fix for the next 7.3.x release,
please use the 'libreoffice-7-3' branch.

If you want to build something cool, unstable, and risky, use master.



[Libreoffice-commits] core.git: Changes to 'libreoffice-7-3-3'

2022-04-12 Thread Christian Lohmaier (via logerrit)
New branch 'libreoffice-7-3-3' available with the following commits:
commit 3032f3067dedc9bc5bb0b58a5e5c2d8933ac49da
Author: Christian Lohmaier 
Date:   Tue Apr 12 21:15:21 2022 +0200

Branch libreoffice-7-3-3

This is 'libreoffice-7-3-3' - the stable branch for the 7.3.3 release.
Only very safe changes, reviewed by three people are allowed.

If you want to commit more complicated fix for the next 7.3.x release,
please use the 'libreoffice-7-3' branch.

If you want to build something cool, unstable, and risky, use master.



[Libreoffice-commits] core.git: Changes to 'libreoffice-7-3-2'

2022-03-09 Thread Christian Lohmaier (via logerrit)
New branch 'libreoffice-7-3-2' available with the following commits:
commit 9995005765b5bce86ada523f13dbe9d6501d2e9d
Author: Christian Lohmaier 
Date:   Wed Mar 9 19:53:08 2022 +0100

Branch libreoffice-7-3-2

This is 'libreoffice-7-3-2' - the stable branch for the 7.3.2 release.
Only very safe changes, reviewed by three people are allowed.

If you want to commit more complicated fix for the next 7.3.x release,
please use the 'libreoffice-7-3' branch.

If you want to build something cool, unstable, and risky, use master.



[Libreoffice-commits] core.git: Changes to 'libreoffice-7-3-1'

2022-02-11 Thread Christian Lohmaier (via logerrit)
New branch 'libreoffice-7-3-1' available with the following commits:
commit 8f238a68ec8d32bcff3bcfdc68344b8c136b747c
Author: Christian Lohmaier 
Date:   Fri Feb 11 12:01:18 2022 +0100

Branch libreoffice-7-3-1

This is 'libreoffice-7-3-1' - the stable branch for the 7.3.1 release.
Only very safe changes, reviewed by three people are allowed.

If you want to commit more complicated fix for the next 7.3.x release,
please use the 'libreoffice-7-3' branch.

If you want to build something cool, unstable, and risky, use master.



[Libreoffice-commits] core.git: Changes to 'libreoffice-7-3-0'

2022-01-12 Thread Christian Lohmaier (via logerrit)
New branch 'libreoffice-7-3-0' available with the following commits:
commit 23ce2041f21a7ba3f149c45a14221b107d5ee646
Author: Christian Lohmaier 
Date:   Wed Jan 12 20:04:22 2022 +0100

Branch libreoffice-7-3-0

This is 'libreoffice-7-3-0' - the stable branch for the 7.3.0 release.
Only very safe changes, reviewed by three people are allowed.

If you want to commit more complicated fix for the next 7.3.x release,
please use the 'libreoffice-7-3' branch.

If you want to build something cool, unstable, and risky, use master.



[Libreoffice-commits] core.git: Changes to 'libreoffice-7-3'

2021-11-25 Thread Christian Lohmaier (via logerrit)
New branch 'libreoffice-7-3' available with the following commits:
commit 4f2fbdbd20c558ba2160350d03149437c26b84df
Author: Christian Lohmaier 
Date:   Thu Nov 25 20:06:01 2021 +0100

Branch libreoffice-7-3

This is 'libreoffice-7-3' - the stable branch for the 7.3.x releases.
The commit rules are different according to the development phase:

A. 7.3.0 beta phase:

   A. any bug fixes are allowed without review
   B. late features need approval by 3 people with different affiliation

B. 7.3.0 rc phase and later:

   A. fixes need approval by one reviewer
   B. late features need approval by 3 more people with different 
affiliation

IMPORTANT: Every developer is responsible for pushing the fixes into all
  appropriate branches. Note that we do not plan any merge
  from this branch to master or vice versa.

Please, help use to make stable and usable release. If you want to build
something cool, unstable, and risky, use master.