I have a question about the structure of the svn. The branch fixes_2_6 still has the version 2.5.1. shouldn't this be set to 2.6.0-RC1.1? to indicate that this is always the newest 2.6.x version (newer than any 2.6 release or candidate ever released from this branch) and as such already newer than 2.6.0-RC1?
2.5.1 for the 2.6 fixes branch seems a bit counterintuitive to me. It seems the RC1 has been tagged and *then* afterwards the tag has been modified to update the version number. Shouldn't this rather have happened the other way around, something like this: in fixes_2_6 change version to 2.6.0-RC1 create tags/release_2_6_0_RC1 in fixes_2_6 change version to 2.6.0-RC1.1 (odd number between two RC) fix bugs... in fixes_2_6 change version to 2.6.0-RC2 create tags/release_2_6_0_RC2 in fixes_2_6 change version to 2.6.0-RC2.1 fix bugs... in fixes_2_6 change version to 2.6.0 (no more RC needed) create tags/release_2_6_0 in fixes_2_6 change version to 2.6.1 fix bugs... so that the fixes branch always at any time has the highest version number of this branch, higher than everything released from this branch so far? Bernd _______________________________________________ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-pascal
