Kathey Marsden wrote:
Rick Hillegas wrote:
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.
I thought the fourth digit was supposed to bump everytime a snapshot
was made. Unfortunately we don't make many snapshots but I think it
would be useful to the community as bugfixes go into the maintenance
release.
Kathey
I've lost track of the snapshot conversation. We produced a couple alpha
snapshots of the trunk last year, before we cut the 10.2 branch. Have we
ever publicly produced snapshots from a branch? I'm not talking about
private snapshots here. I'm talking about distributions which are
published for the community to test, as described at the end of the
release instructions page:
http://wiki.apache.org/db-derby/DerbySnapshotOrRelease
I seem to recall that there was some uneasiness about using Apache
websites to publish these unvetted snapshots.
-Rick
