[Lazarus] revision numbers of each SVN tag?

Graeme Geldenhuys graemeg.lists at gmail.com
Wed Apr 15 15:36:41 CEST 2009

On Wed, Apr 15, 2009 at 3:02 PM, Florian Klaempfl
<florian at freepascal.org> wrote:
>> 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?

Do you mean... have I tested a release candidate when it was
announced. It so, then the answer is yes.

> 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.

You guys are talking in circles! Now you tell be that branches and
tags are different, yet earlier I was explicitly told that tags and
branches are identical in SubVersion.  In in actual fact, there should
be NO difference in creating a release from a branch compared to a
release from a tag.

Form your quote above, nobody can ensure that all release builders
have the exact same revision when tags are used either. After all,
merges and patches have been applied to tags - exactly the same thing
as is done to branches!  This was EXACTLY the point I was trying to
make form the start! Prohibit all read/write access developers from
writing to tags. "pre-xxxx" branches will work perfectly and once all
release builders are happy, THEN ONLY create a tag.

The point I made earlier. I checkout the tag "lazarus-0.9.26", then
Vincent applies patches or merges something in there. I talk on the
mailing list about tag "lazarus-0.9.26", when my revision is different
from Vincent's revision.

> At cvs times we did this for fpc and we had to lock the branch to
> prevent commits (btw: can git lock branches ;)?),

Yes, you use non-lightweight tags for that.

  - Graeme -

fpGUI - a cross-platform Free Pascal GUI toolkit

More information about the Lazarus mailing list