On Tue, 2006-11-14 at 08:20 +0100, [EMAIL PROTECTED] wrote:
- you specify a base label
- you specify all bugs form the trunk/branch that should be included in a
new build
- A new label is created basing on that
Is it necessary that a new label(branch) is specified ? I see two
possible needs here:
- Copy from the base branch into a new branch. Then apply all changes
described by the list of bugs into new branch.
yep
- Apply the list of bugs directly onto the base branch. (e.g. merge work
on a branch into the main trunk).
Nop
So, how about if no new branch is supplied, then the changes described
by the bug list are applied directly to the base branch. If one is
supplied, then a copy is first made from the base.
Let me explain the idea behind my understanding of incremental builds -the
results of builds are kept only in /tags as labels:
Let's say that we have development on:
/trunk
/branches/Atlanta_release
/branches/Limepoint_release
Let's concentrate on
/branches/Limepoint_release
We had 3 releases here:
/tags/LIMEPOINT_0_0_0_1_DEV
/tags/LIMEPOINT_0_0_0_2_DEV
/tags/LIMEPOINT_0_0_0_3_DEV
We also implemented following bugs or tasks on /branches/Limepoint_release
that are not included in /tags/LIMEPOINT_0_0_0_3_DEV:
700 (closed),701 (closed), 711 (closed), 712 (assigned) - that's the top of
/branches/Limepoint_release
We'd like to include only 700 & 701 in /tags/LIMEPOINT_0_0_0_4_DEV, let's
assume that there was no problem with that so 701, 702 can be included in
next releases.
We use a PHP build generator page in mantis - an interface to perl
scripts - I'm going to write - you specify there:
Base: /tags/LIMEPOINT_0_0_0_3_DEV
Target: /tags/LIMEPOINT_0_0_0_4_DEV
Bug list: 700,701 (when entered it will display all affected files)
Then click: "create build"
The operation of merging the files from bugs 701 & 700 will be associated
with a separate automatically generated bug in Mantis is a special BUILDS -
lets say 800 with automatically
generated references to 700,701 there and extra comments descibing the
build if necessary
the top of /branches/Limepoint_release remains the same
Best regards
Marek
_______________________________________________
scmbug-users mailing list
[email protected]
http://lists.mkgnu.net/cgi-bin/mailman/listinfo/scmbug-users
