Daniel John Debrunner wrote:
Rick Hillegas wrote:
Perhaps the disconnect arises from the different patch usage patterns
at IBM and Sun. It seems to me that IBM tends to not bump the patch
id when generating a patch, but Sun does. Sun's usage implies that,
on the eve of building 10.3.2.0, the head of the 10.3 branch might
actually be tagged as 10.3.1.9.
What IBM or Sun do is not relevant. Only what happens in the Derby svn
matters.
Dan.
Right. What I am pointing out, however, is that there seem to be two
different assumptions current in the community. Some people in the
community assume that the release id on the branch will stay pegged at
10.3.1.5 until a release manager builds a bugfix release on the 10.3
branch. Other people in the community assume that the patch part of the
release id may increment several times before the bugfix release.
-Rick
