[platform-text-dev] 3.1.1 Fixing Rules

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]

[platform-text-dev] 3.1.1 Fixing Rules

From: Daniel Megert <daniel_megert@xxxxxxxxxx>
Date: Mon, 11 Jul 2005 12:17:33 +0200
Delivered-to: platform-text-dev@xxxxxxxxxxx
List-archive: <http://eclipse.org/pipermail/platform-text-dev>
List-help: <mailto:platform-text-dev-request@eclipse.org?subject=help>
List-subscribe: <https://dev.eclipse.org/mailman/listinfo/platform-text-dev>, <mailto:platform-text-dev-request@eclipse.org?subject=subscribe>
List-unsubscribe: <https://dev.eclipse.org/mailman/listinfo/platform-text-dev>, <mailto:platform-text-dev-request@eclipse.org?subject=unsubscribe>

The rules for releasing code into the R3_1_maintenance branch are as
follows:

- component lead must approve all work on a component.
- no changes are to be released without prior approval and associated bug
report tagged 3.1.1
- two additional committers must check all code changes
- the person who reported bug should verify the bug in a 3.1.1 build

Dani

Prev by Date: [platform-text-dev] 3.1 RC4 Fixes From Platform Text and JDT Text For N20050623-0010
Next by Date: [platform-text-dev] Phil Coulthard/Toronto/IBM is out of the office.
Previous by thread: [platform-text-dev] 3.1 RC4 Fixes From Platform Text and JDT Text For N20050623-0010
Next by thread: [platform-text-dev] 3.2 M1 test plan
Index(es):
- Date
- Thread

Breadcrumbs