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: svn commit: r742512 - /db/derby/code/branches/10.4/tools/ant/properties/release.properties
Date Mon, 09 Feb 2009 18:17:22 GMT
On Mon, Feb 9, 2009 at 6:09 AM,  <rhillegas@apache.org> wrote:
> Author: rhillegas
> Date: Mon Feb  9 14:09:56 2009
> New Revision: 742512
>
> URL: http://svn.apache.org/viewvc?rev=742512&view=rev
> Log:
> Bump the fourth digit of the 10.4 release id.
>
> Modified:
>    db/derby/code/branches/10.4/tools/ant/properties/release.properties
>
> Modified: db/derby/code/branches/10.4/tools/ant/properties/release.properties
> URL: http://svn.apache.org/viewvc/db/derby/code/branches/10.4/tools/ant/properties/release.properties?rev=742512&r1=742511&r2=742512&view=diff
> ==============================================================================
> --- db/derby/code/branches/10.4/tools/ant/properties/release.properties (original)
> +++ db/derby/code/branches/10.4/tools/ant/properties/release.properties Mon Feb  9 14:09:56
2009
> @@ -15,10 +15,10 @@
>
>  #Wed Apr 16 19:11:46 CEST 2008
>  major=10
> -maint=2000001
> +maint=2000002
>  drdamaint=0
>  minor=4
>  eversion=10.4
> -copyright.comment=Copyright 1997, 2008 The Apache Software Foundation or its licensors,
as applicable.
> +copyright.comment=Copyright 1997, 2009 The Apache Software Foundation or its licensors,
as applicable.
>  beta=false
>  vendor=The Apache Software Foundation
>
>
>

Rick,

I don't think you can just bump the version number like this.

I understand it's confusing to customers because Sun has included a
10.4.2.1 build as JavaDB. But the official apache release is still
10.4.2.0. I saw you And added a 10.4.2.2 as fix version to one bug -
to be consistent, you should go through all bugs that got fixed in
10.4 since Sun's build and mark them 10.4.2.2 also? But don't do that
yet, let's discuss this first!

Note, I don't personally have a big dependency on 10.4 at the moment,
but it's the principle of changing policy like this.

Basically, if you don't use an official Apache derby build in your
product, then the only clue your customers have is the build number.
I've used this approach for customers that needed bug fixes.
Kathey and Knut briefly discussed bumping the fourth digit with
DERBY-3919: https://issues.apache.org/jira/browse/DERBY-3919?focusedCommentId=12641912#action_12641912
Maybe we should extend that discussion?

An alternative to suddently bump the number & still minimize confusion
for Sun's customers is to call a vote on the 10.4.2.1 as it is now.

Either way, I think you should revert this change until we've discussed it.

Thx,
Myrna

Mime
View raw message