gnash-commit
[Top][All Lists]
Advanced

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

Re: [Gnash-commit] [SCM] Gnash branch, release, created. release_0_8_9_s


From: Gabriele Giacone
Subject: Re: [Gnash-commit] [SCM] Gnash branch, release, created. release_0_8_9_start-9-ga06e27b
Date: Fri, 04 Feb 2011 01:08:44 +0100
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.9) Gecko/20100918 Iceowl/1.0b2 Icedove/3.1.4

Hi,
I've just created a branch named "release" from "release_0_8_9" because
makedeb doesn't like underscores in branch name.

BTW, IMHO release branches become useless after release.
I'd suggest to use tags following something like:

It's release time,
- create "release" branch
- changes,changes,changes
- tag last commit as for instance "0.8.9"
- merge "release" branch into "master"
- remove "release" branch

There would be a tag per release version and there would exist just
topic branches like "openvg".
IMHO cleaner, less confusing.

What do you think?

Gabriele


On 02/04/2011 12:33 AM, Gabriele Giacone wrote:
> This is an automated email from the git hooks/post-receive script. It was
> generated because a ref change was pushed to the repository containing
> the project "Gnash".
> 
> The branch, release has been created
>         at  a06e27b5d5c2cee57c3a7c9281b0bebcc0a04b0b (commit)
> 
> - Log -----------------------------------------------------------------
> http://git.savannah.gnu.org/cgit//commit/?id=a06e27b5d5c2cee57c3a7c9281b0bebcc0a04b0b



reply via email to

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