[Lazarus] revision numbers of each SVN tag?

Florian Klaempfl florian at freepascal.org
Wed Apr 15 15:02:05 CEST 2009

Graeme Geldenhuys schrieb:
> 2009/4/15 Flávio Etrusco <flavio.etrusco at gmail.com>:
>> As I said previously (and was completely ignored ;-), with SVN one can
>> rely on repository revisions.
>> And if people don't like that, they can use a series of "pre" tags.
>> And probably a "pre" branch.
> Brilliant idea.  Create a "pre-0.9.26" branch (or tag <yuck>) and
> start the release process. 2-4 months later if anything is broken,
> merge and patch that branch at will. Test again 

Did you ever working on testing a lazarus or fpc release?

> and if all is well,
> then create a "lazarus_0.9.26" tag (never to be touched because it's a
> released version).
> How difficult is that??? 

Very difficult. If a release is created from a branch, nobody can ensure
that all release builders built the release candidate from exactly the
same revision, if they don't, things might be broken when the final
release should be built.

At cvs times we did this for fpc and we had to lock the branch to
prevent commits (btw: can git lock branches ;)?), but nevertheless it
caused confusion. So we decided to built from tags and move the tag by
merging if really needed. Believe me, from 15 years fpc development,
we've a lot of experience how to built a release of something complex
like lazarus or fpc (fpc has even a defined release procedure, see

More information about the Lazarus mailing list