<commit_before>---
title: "Gerrit 3.3.0-rc6 release (in development)"
permalink: 3.3.html
hide_sidebar: true
hide_navtoggle: true
toc: true
---

Download: **[3.3.0-rc6](https://gerrit-releases.storage.googleapis.com/gerrit-3.3.0-rc6.war)**

Documentation: **[3.3.0-rc6](https://gerrit-documentation.storage.googleapis.com/Documentation/3.3.0/index.html)**

## Release highlights

* Java 11 by default for Gerrit

* New logs timestamp format

* Attention Set

## Important notes

### Default support for Java 11

The java language level is now set to Java 11 by default for Gerrit.

* [Issue 13494](https://bugs.chromium.org/p/gerrit/issues/detail?id=13494);
  Generate a Java 11 Eclipse project by default

* Update dev-{eclipse,intellij} development for Java 11.

### Schema changes

This release contains schema changes. To upgrade:

``` sh
  java -jar gerrit.war init -d site_path
```

Upgrading to this schema version (184) renames the `Non-Interactive Users`
group to `Service Users`.

### Breaking changes

* [New logs timestamp format](http://gerrit-documentation.storage.googleapis.com/Documentation/3.3.0/logs.html):

  The new format supports both ISO-8601 and RFC3339, which means that if you are
  parsing it as general ISO-8601 it should work as before. However you will be
  affected if you are parsing the timestamp with a static format.

### ChangeAttributeFactory deprecated and ChangePluginDefinedInfoFactory supported

Similar to the ChangeAttributeFactory, a ChangePluginDefinedInfoFactory allows
plugins to [provide additional data in change results](http://gerrit-documentation.storage.googleapis.com/Documentation/3.3.0/dev-plugins.html#query_attributes).
ChangePluginDefinedInfoFactory has the advantage that it allows plugins to know
the full set of changes up front so that they can do bulk operations.

ChangeAttributeFactory will be removed in the next release.

## Native packaging

## New features

* [Attention Set](http://gerrit-documentation.storage.googleapis.com/Documentation/3.3.0/user-attention-set.html):

  For every change Gerrit maintains an "Attention Set" with users that are
  currently expected to act on the change. Both on the dashboard and on the
  change page, this is expressed by an arrow icon before the user name.

  Enabled by default.
  The former assignee feature is therefore now disabled by default.

* Reply dialog posts patchset level comments instead of change messages.

### REST API changes

* Reject REST requests with invalid enum values as bad request

* Expose 'Service User' tag on the REST API

* Add endpoints to allow enhancement on submit requirements

* Add parameter for added reviewers on reply-reviewers endpoint

* Add an alternate `CreateChange` endpoint

* [Issue 13357](https://bugs.chromium.org/p/gerrit/issues/detail?id=13357);
  Add the work_in_progress option to the revert and revertSubmission endpoints

## End-to-end tests<commit_msg>Update 3.3 release notes<commit_after>---
title: "Gerrit 3.3.0-rc6 release (in development)"
permalink: 3.3.html
hide_sidebar: true
hide_navtoggle: true
toc: true
---

Download: **[3.3.0-rc6](https://gerrit-releases.storage.googleapis.com/gerrit-3.3.0-rc6.war)**

Documentation: **[3.3.0-rc6](https://gerrit-documentation.storage.googleapis.com/Documentation/3.3.0/index.html)**

## Release highlights

* Java 11 by default for Gerrit

* New logs timestamp format

* Attention Set

## Important notes

### Default support for Java 11

The java language level is now set to Java 11 by default for Gerrit.

* [Issue 13494](https://bugs.chromium.org/p/gerrit/issues/detail?id=13494);
  Generate a Java 11 Eclipse project by default

* Update dev-{eclipse,intellij} development for Java 11.

### Schema changes

This release contains schema changes. To upgrade:

``` sh
  java -jar gerrit.war init -d site_path
```

Upgrading to this schema version (184) renames the `Non-Interactive Users`
group to `Service Users`.

### Breaking changes

* [New logs timestamp format](http://gerrit-documentation.storage.googleapis.com/Documentation/3.3.0/logs.html):

  The new format supports both ISO-8601 and RFC3339, which means that if you are
  parsing it as general ISO-8601 it should work as before. However you will be
  affected if you are parsing the timestamp with a static format.

### ChangeAttributeFactory deprecated and ChangePluginDefinedInfoFactory supported

Similar to the ChangeAttributeFactory, a ChangePluginDefinedInfoFactory allows
plugins to [provide additional data in change results](http://gerrit-documentation.storage.googleapis.com/Documentation/3.3.0/dev-plugins.html#query_attributes).
ChangePluginDefinedInfoFactory has the advantage that it allows plugins to know
the full set of changes up front so that they can do bulk operations.

ChangeAttributeFactory will be removed in the next release.

## Native packaging

## New features

* [Attention Set](http://gerrit-documentation.storage.googleapis.com/Documentation/3.3.0/user-attention-set.html):

  For every change Gerrit maintains an "Attention Set" with users that are
  currently expected to act on the change. Both on the dashboard and on the
  change page, this is expressed by an arrow icon before the user name.

  Enabled by default.
  The former assignee feature is therefore now disabled by default.

* Reply dialog posts patchset level comments instead of change messages.

* [Issue 13670](https://bugs.chromium.org/p/gerrit/issues/detail?id=13670);
  Introduce cache.openFiles setting in gerrit.config.

  Persistent caches might require the allocation of additional file
  descriptors depending on their configuration and backend engine.
  This new setting allows the gerrit.sh to be aware of that and increase the
  number of files accordingly before starting Gerrit.

  E.g. when swapping the default H2 persistent cache implementation with the
  [chronicle-map implementation](https://gerrit.googlesource.com/modules/cache-chroniclemap/+/refs/heads/stable-3.3)
  the number of open files needs raising, since the latter is bound to open more
  file descriptors, mostly due to its usage of memory mapped files.

### REST API changes

* Reject REST requests with invalid enum values as bad request

* Expose 'Service User' tag on the REST API

* Add endpoints to allow enhancement on submit requirements

* Add parameter for added reviewers on reply-reviewers endpoint

* Add an alternate `CreateChange` endpoint

* [Issue 13357](https://bugs.chromium.org/p/gerrit/issues/detail?id=13357);
  Add the work_in_progress option to the revert and revertSubmission endpoints

## End-to-end tests
{'fraction_non_alphanumeric': 0.08321964529331514, 'fraction_numerical': 0.02501136880400182, 'mean_word_length': 4.54453781512605, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 10, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 2, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '4862000', 'n_tokens_mistral': 2014, 'n_tokens_neox': 1802, 'n_words': 728}