[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[bug-gettext] branching plans

From: Daiki Ueno
Subject: [bug-gettext] branching plans
Date: Mon, 21 Jan 2013 11:53:44 +0900
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3.50 (gnu/linux)

Hi all,

For 0.19, gettext will get more programming language features including
JavaScript and Python 3 brace format support, as well as bug fixes.
Currently both parsers share a large portion of the code with other
parsers.  For example, x-javascript.c is based on x-python.c and
format-python-brace.c is based on format-perl-brace.c.

To make the reviews easier (with git diff --find-copies-harder etc), and
to keep the master branch stable, it might make sense to define some
branch policy.

Currently I plan to follow the Automake practice.  That means to create
a "maint" branch, where all the bug fixes shall be checked in first, and
merge the changes periodically to the master.  And the topic branches
for the features will be branched off from "maint".

What do people think?

Daiki Ueno

reply via email to

[Prev in Thread] Current Thread [Next in Thread]