db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Myrna van Lunteren" <m.v.lunte...@gmail.com>
Subject Re: [VOTE CANCELLED] release candidate
Date Fri, 11 Apr 2008 19:28:30 GMT
On 4/11/08, Dyre.Tjeldvoll@sun.com <Dyre.Tjeldvoll@sun.com> wrote:
> Bryan Pendleton <bpendleton@amberpoint.com> writes:
> >>> I plan to do this as soon as the fix for DERBY-3347 has been merged to
> >>> the 10.4 branch, and then call for a vote on the new RC.
> >
> > I'm not sure I understand why the availability of additional fixes
> > required the cancellation of the previous vote.
> It probably doesn't. I just chose that subject because the 10.3 Feature
> Release Summary on http://wiki.apache.org/db-derby/DerbyTenThreeRelease,
> says "Sanity Testing and Voting (Cancelled - blocker DERBY-1963)".
> > It seems to me that there are always additional fixes on the horizon.
> >
> > I don't think we were voting on whether was to be the
> > actual *release*;
> Ummm, I thought we were. Had it not been for DERBY-3347 I was going to
> put it on the mirrors and so on (provided it got PMC approval).
> > we were simply voting on whether it was an
> > acceptable release *candidate* for making available for advanced
> > users interested in helping us test the software prior to release.
> So you you considered to be a BETA release candidate that, once
> approved through a vote would become a BETA release that users could try
> out? And that based on their feedback there would be a proper release
> candidate that, if approved, would turn into a proper release?
> That was not my plan. Sorry if I gave that impression. The current
> description of the release process only mentions one vote, and my
> understanding is that it determines if a release candidate can
> become a release.
> --
> dt
I too had understood a Release Candidate to become a Release once approved.

Now that there is a plan for a new release candidate, I think maybe
the javadoc should be fixed?
There are the following errors:

  [javadoc] Loading source file
  [javadoc] Loading source file
  [javadoc] Loading source file
  [javadoc] C:\svn\10.4\java\engine\org\apache\derby\iapi\error\SQLWarningFactory.java:46:
warning - Tag @link: reference not found: SQLState
  [javadoc] C:\svn\10.4\java\engine\org\apache\derby\iapi\error\SQLWarningFactory.java:63:
warning - Tag @link: reference not found: SQLState
  [javadoc] C:\svn\10.4\java\engine\org\apache\derby\iapi\jdbc\DRDAServerStarter.java:107:
warning - @param argument "address" is not a parameter name.
  [javadoc] C:\svn\10.4\java\engine\org\apache\derby\iapi\jdbc\DRDAServerStarter.java:107:
warning - Tag @see: reference not found: NetworkServerControl
  [javadoc] C:\svn\10.4\java\engine\org\apache\derby\impl\store\access\sort\ExternalSortFactory.java:129:
warning - @returns is an unknown tag.
  [javadoc] C:\svn\10.4\java\engine\org\apache\derby\impl\store\access\sort\UniqueWithDuplicateNullsExternalSortFactory.java:37:
warning - Tag @see: reference not found:
  [javadoc] C:\svn\10.4\java\engine\org\apache\derby\impl\store\access\sort\UniqueWithDuplicateNullsExternalSortFactory.java:44:
warning - Tag @see: reference not found:
  [javadoc] C:\svn\10.4\java\engine\org\apache\derby\impl\store\replication\master\MasterController.java:290:
warning - Tag @see: reference not found:
  [javadoc] C:\svn\10.4\java\engine\org\apache\derby\authentication\SystemPrincipal.java:47:
warning - Tag @see: can't find name in java.security.Principal
  [javadoc] C:\svn\10.4\java\engine\org\apache\derby\iapi\sql\dictionary\IndexRowGenerator.java:275:
warning - Tag @see:  can't find isisUniqueWithDuplicateNulls in
  [javadoc] C:\svn\10.4\java\engine\org\apache\derby\impl\sql\execute\CreateIndexConstantAction.java:140:
warning - @param argument "isUniqueWithDuplicateNulls" is not a
parameter name.
  [javadoc] C:\svn\10.4\java\engine\org\apache\derby\impl\sql\execute\UniqueWithDuplicateNullsIndexSortObserver.java:56:
 warning - @param argument "distinct" is not a parameter name.
  [javadoc] C:\svn\10.4\java\engine\org\apache\derby\impl\sql\execute\UniqueWithDuplicateNullsIndexSortObserver.java:74:
 warning - @returns is an unknown tag.
  [javadoc] 13 warnings

Also, I'd like to see if 1 test bug can be backported that I ran into
when I ran with weme6.1 (i.e. using IBM's JSR169 implementation):
DERBY-3548 (fixed in 10.5) I just may not have time to look at it further today.


View raw message