Francois Orsini wrote:
I think you meant 'org.apache.derby.common' in your examples.
Yes, thanks.
Now, if the common package versioning is well automated as part of
generating a new release, then it is probably ok to have a new version
being generated for every release.
Are you thinking that we would always see 'org.apache.derby.common' in
the source tree and that the common pkg version suffix would only be
added when a (new) release gets generated?
Well, this is a good question, if you're asking about what should the
package name be in the trunk. Yes, I suppose it could just be
'org.apache.derby.common' and the rename happens only when a branch is
made for a release. I am trying to think if this would cause any issues
for people pulling the nightly builds -- I can't think of any, unless
people try to mix versions from old and new nightly builds, in which
case I think they're really on their own :)
An alternate approach is to do the rename on the trunk just prior to
making the branch, so the trunk package name always matches the most
recent release branch. But this doesn't seem as clean...
David
begin:vcard
fn:David W Van Couvering
n:Van Couvering;David W
org:Sun Microsystems, Inc.;Database Technology Group
email;internet:[EMAIL PROTECTED]
title:Senior Staff Software Engineer
tel;work:510-550-6819
tel;cell:510-684-7281
x-mozilla-html:TRUE
version:2.1
end:vcard
