again, another 10.3.1. release candidate?

[Myrna van Lunteren <m....@gmail.com>]

Hi,

There was a discussion ensuing from DERBY-2896, which I think should
be a general discussion item, following mamta's check-in for a fix for
that critical issue.


Knut Anders Wrote:
> >The changes in metadata.properties will not be picked up when you upgrade from 10.3.1.x to 10.3.2.x.
>
Kathey replied:
> This filed as DERBY-1107 and I think is a good reason to have a new release candidate.  I think other critical issues such as DERBY-2437 and the regression DERBY-2892 might be worth waiting for too if they can be fixed in short order.  I wouldn't veto a release at this point but would probably vote -0.


It seems to me that even though Kathey doesn't want to hold up the
release, she really doesn't want a release without this fix.
Which to me sounds like a new release candidate, which, as we've got a
vote outstanding, means holding up the release. :-)

But Kathey's email poses some options
1. I can do a fairly quick turn-around and make another release
candidate after Mamta backports the fix to 10.3. If I can build the
files tonight or tomorrow morning early, I can test, and call a vote
around noon, that would give us until July 26th noon (PDT) and I could
maybe still close the vote and hope that the maven work and web page
work can be finished on that day, or leave it to Rick to do that part
once he's back the week after.

2. We can wait until someone fixes DERBY-2892 for 10.3. I have not
heard anything positive, nor a time frame for such a fix. If a fix
happens before the 26th, I can generate new build files and open the
voting, but someone else (Rick when he's back form
vacation/conference?) will have to finish up the work for this
release.

3. We can wait even further until other critical issues such as
DERBY-2437 are fixed. I want to point out, that no has volunteered to
own that one at this point, so we might be waiting indefinitely. I
can, as I have suggested before, pick up the release work in
September, and we can see how far the fixes are then. Or someone else
can volunteer.

Kathey, please be explicit, which 'other' issues except DERBY-2437 do
you think are necessary to receive a fix?


Myrna

Re: again, another 10.3.1. release candidate?

[Kathey Marsden <km...@sbcglobal.net>]

Myrna van Lunteren wrote:
> Hi,
>
> There was a discussion ensuing from DERBY-2896, which I think should
> be a general discussion item, following mamta's check-in for a fix for
> that critical issue.
>
>
> Knut Anders Wrote:
>> >The changes in metadata.properties will not be picked up when you 
>> upgrade from 10.3.1.x to 10.3.2.x.
>>
> Kathey replied:
>> This filed as DERBY-1107 and I think is a good reason to have a new 
>> release candidate.  I think other critical issues such as DERBY-2437 
>> and the regression DERBY-2892 might be worth waiting for too if they 
>> can be fixed in short order.  I wouldn't veto a release at this point 
>> but would probably vote -0.
>
>
> It seems to me that even though Kathey doesn't want to hold up the
> release, she really doesn't want a release without this fix.
> Which to me sounds like a new release candidate, which, as we've got a
> vote outstanding, means holding up the release. :-)
>
> But Kathey's email poses some options
> 1. I can do a fairly quick turn-around and make another release
> candidate after Mamta backports the fix to 10.3. If I can build the
> files tonight or tomorrow morning early, I can test, and call a vote
> around noon, that would give us until July 26th noon (PDT) and I could
> maybe still close the vote and hope that the maven work and web page
> work can be finished on that day, or leave it to Rick to do that part
> once he's back the week after.
>
> 2. We can wait until someone fixes DERBY-2892 for 10.3. I have not
> heard anything positive, nor a time frame for such a fix. If a fix
> happens before the 26th, I can generate new build files and open the
> voting, but someone else (Rick when he's back form
> vacation/conference?) will have to finish up the work for this
> release.
>
> 3. We can wait even further until other critical issues such as
> DERBY-2437 are fixed. I want to point out, that no has volunteered to
> own that one at this point, so we might be waiting indefinitely. I
> can, as I have suggested before, pick up the release work in
> September, and we can see how far the fixes are then. Or someone else
> can volunteer.
>
> Kathey, please be explicit, which 'other' issues except DERBY-2437 do
> you think are necessary to receive a fix?
>
>
Well, since DERBY-2905 is a regression, I would love to see that one 
fixed, but I wouldn't call it necessary.

I would like to see the analysis of DERBY-2656 complete.  I can finish 
that by Monday.

Ramin is I think close to a patch for DERBY-2925 which would fix 
DERBY-2437, but I am not sure how strongly Dag feels about that being 
the wrong solution.  It has the advantage of being a solution.

DERBY-1107 is I think not an easy bug to fix, so I think we should have 
a release candidate for DERBY-2896 to avoid having to fix it.  That is 
the primary issue.

So my vote would be to plan to make a new release candidate on Monday 
and hopefully we will be able to make a dent in some of these  issues. 
People can continue banging away on 10.3 and see if we can pop more 
issues.  Perhaps we'll even get  more bugs fixed. 

Kathey

Re: again, another 10.3.1. release candidate?

[Mamta Satoor <ms...@gmail.com>]

Myrna, I have run critical tests on my 10.3 codeline after merge and things
are running fine so far. I will go ahead and back port my changes into
10.3codeline because I will be gone for the rest of the evening and in
case we
decide to cut a 10.3.1.x branch before that. I will tackle the metadata
upgrade issue only if it turns out that my changes will not make into
10.3.1.x

Mamta


On 7/18/07, Myrna van Lunteren <m....@gmail.com> wrote:
>
> Hi,
>
> There was a discussion ensuing from DERBY-2896, which I think should
> be a general discussion item, following mamta's check-in for a fix for
> that critical issue.
>
>
> Knut Anders Wrote:
> > >The changes in metadata.properties will not be picked up when you
> upgrade from 10.3.1.x to 10.3.2.x.
> >
> Kathey replied:
> > This filed as DERBY-1107 and I think is a good reason to have a new
> release candidate.  I think other critical issues such as DERBY-2437 and the
> regression DERBY-2892 might be worth waiting for too if they can be fixed in
> short order.  I wouldn't veto a release at this point but would probably
> vote -0.
>
>
> It seems to me that even though Kathey doesn't want to hold up the
> release, she really doesn't want a release without this fix.
> Which to me sounds like a new release candidate, which, as we've got a
> vote outstanding, means holding up the release. :-)
>
> But Kathey's email poses some options
> 1. I can do a fairly quick turn-around and make another release
> candidate after Mamta backports the fix to 10.3 . If I can build the
> files tonight or tomorrow morning early, I can test, and call a vote
> around noon, that would give us until July 26th noon (PDT) and I could
> maybe still close the vote and hope that the maven work and web page
> work can be finished on that day, or leave it to Rick to do that part
> once he's back the week after.
>
> 2. We can wait until someone fixes DERBY-2892 for 10.3. I have not
> heard anything positive, nor a time frame for such a fix. If a fix
> happens before the 26th, I can generate new build files and open the
> voting, but someone else (Rick when he's back form
> vacation/conference?) will have to finish up the work for this
> release.
>
> 3. We can wait even further until other critical issues such as
> DERBY-2437 are fixed. I want to point out, that no has volunteered to
> own that one at this point, so we might be waiting indefinitely. I
> can, as I have suggested before, pick up the release work in
> September, and we can see how far the fixes are then. Or someone else
> can volunteer.
>
> Kathey, please be explicit, which 'other' issues except DERBY-2437 do
> you think are necessary to receive a fix?
>
>
> Myrna
>

[OT - votes] Re: again, another 10.3.1. release candidate?

[Stanley Bradbury <St...@gmail.com>]

Daniel John Debrunner wrote:
> Stanley Bradbury wrote:
>
>> As I indicated with my [-1] vote to the 10.3.1.2 VOTE thread: I need 
>> the fix for Derby-2896 to be part of official 10.3 release - this 
>> requires that new release candidtate be created (presumably 10.3.1.3?)
>
> Just a gentle reminder, no-one can veto a release. Thus anyone's 
> desires for a specific bug to be fixed do not impose any requirement 
> on a release manager. It is ok for a release to proceed "ignoring" -1 
> votes as long as it has the required number of +1 PMC votes.
>
> Though, I think if a release does have -1 votes that it is wise for 
> the release manager to consider them before putting the release on the 
> mirrors.
>
> Dan.
>
>
>
Of course.  I mentioned my vote and stated the importance (to me) of  
having this fix in the context of this thread asking "..another release 
candidate?", nothing more implied.

Re: again, another 10.3.1. release candidate?

[Myrna van Lunteren <m....@gmail.com>]

On 7/19/07, Daniel John Debrunner <dj...@apache.org> wrote:
> Just a gentle reminder, no-one can veto a release. Thus anyone's desires
> for a specific bug to be fixed do not impose any requirement on a
> release manager. It is ok for a release to proceed "ignoring" -1 votes
> as long as it has the required number of +1 PMC votes.
>
> Though, I think if a release does have -1 votes that it is wise for the
> release manager to consider them before putting the release on the mirrors.
>
> Dan.
>
>
>
Thx for that reminder Dan. My choice for another release candidate is
not the -1 vote per se (although it does point to a concern with
10.3.1.2), but rather the impact of not having the fix for DERBY-2896
in it; without the fix it becomes necessary to fix DERBY-1107 which
was indicated as a non-trivial change.

Myrna

Re: again, another 10.3.1. release candidate?

[Daniel John Debrunner <dj...@apache.org>]

Stanley Bradbury wrote:

> As I indicated with my [-1] vote to the 10.3.1.2 VOTE thread: I need the 
> fix for Derby-2896 to be part of official 10.3 release - this requires 
> that new release candidtate be created (presumably 10.3.1.3?)

Just a gentle reminder, no-one can veto a release. Thus anyone's desires 
for a specific bug to be fixed do not impose any requirement on a 
release manager. It is ok for a release to proceed "ignoring" -1 votes 
as long as it has the required number of +1 PMC votes.

Though, I think if a release does have -1 votes that it is wise for the 
release manager to consider them before putting the release on the mirrors.

Dan.

Re: again, another 10.3.1. release candidate?

[Myrna van Lunteren <m....@gmail.com>]

I've read the emails on this thread carefully...

I agree that the fix for 2896 should be in, considering that if we
make a release without it, more work is needed for future releases.
So, I need to roll a new release.
I marked it blocker, and resolved it based on Mamta and Kathey's info
in the issue, as fixed in 10.4 and 10.3.1.3.

However, although I understand the input from Kathey and Mamta
regarding Kathey's incomplete testing of the collation functionality,
I am thinking of not waiting for Monday, because:
 - none of the current issues is marked blocker for 10.3.1
 - if I call a new vote for a release today, I can still round up most
release work by July 26, and Henri can still finish up the testing.
 - re individual issues mentioned by Kathey:
   - DERBY-2905; yes it's a regression, but it was a regression from
10.1 to 10.3, not from 10.2 to 10.3, and no one has signed up to work
on it.
   - Ramin may be close to a fix for DERBY-2925: which would fix DERBY-2437;
     Dag has voiced concern about the proposed solution. I think while
that discussion is going on we should not implement the proposed fix.
This issue, although of concern, again, is not marked as blocker nor a
regression in the strictest sense.
    - analysis of DERBY-2656 can be finished by Monday.
    If your analysis finds further blocker issues, and they get fixed,
we can roll (yet) another release candidate, and then definitely
someone else will have to put the finishing touches on.

Myrna

Re: again, another 10.3.1. release candidate?

[Stanley Bradbury <St...@gmail.com>]

Myrna van Lunteren wrote:
> Hi,
>
> There was a discussion ensuing from DERBY-2896, which I think should
> be a general discussion item, following mamta's check-in for a fix for
> that critical issue.
>
>
> Knut Anders Wrote:
>> >The changes in metadata.properties will not be picked up when you 
>> upgrade from 10.3.1.x to 10.3.2.x.
>>
> Kathey replied:
>> This filed as DERBY-1107 and I think is a good reason to have a new 
>> release candidate.  I think other critical issues such as DERBY-2437 
>> and the regression DERBY-2892 might be worth waiting for too if they 
>> can be fixed in short order.  I wouldn't veto a release at this point 
>> but would probably vote -0.
>
>
> It seems to me that even though Kathey doesn't want to hold up the
> release, she really doesn't want a release without this fix.
> Which to me sounds like a new release candidate, which, as we've got a
> vote outstanding, means holding up the release. :-)
>
> But Kathey's email poses some options
> 1. I can do a fairly quick turn-around and make another release
> candidate after Mamta backports the fix to 10.3. If I can build the
> files tonight or tomorrow morning early, I can test, and call a vote
> around noon, that would give us until July 26th noon (PDT) and I could
> maybe still close the vote and hope that the maven work and web page
> work can be finished on that day, or leave it to Rick to do that part
> once he's back the week after.
>
> 2. We can wait until someone fixes DERBY-2892 for 10.3. I have not
> heard anything positive, nor a time frame for such a fix. If a fix
> happens before the 26th, I can generate new build files and open the
> voting, but someone else (Rick when he's back form
> vacation/conference?) will have to finish up the work for this
> release.
>
> 3. We can wait even further until other critical issues such as
> DERBY-2437 are fixed. I want to point out, that no has volunteered to
> own that one at this point, so we might be waiting indefinitely. I
> can, as I have suggested before, pick up the release work in
> September, and we can see how far the fixes are then. Or someone else
> can volunteer.
>
> Kathey, please be explicit, which 'other' issues except DERBY-2437 do
> you think are necessary to receive a fix?
>
>
> Myrna
>
As I indicated with my [-1] vote to the 10.3.1.2 VOTE thread: 
I need the fix for Derby-2896 to be part of official 10.3 release - this 
requires that new release candidtate be created (presumably 10.3.1.3?)

Thanks

Re: again, another 10.3.1. release candidate?

[Manjula Kutty <ma...@gmail.com>]

In my openion we should go for a release (if we can include Mamta's fix,
that will be great). But not to wait for the bugs which are not picked by
anyone. And then may be in September we can have a bugfix release. As far,
for me RC2 tests are progressing well. So nothing stops me to vote +1

Thanks
Manjula


On 7/18/07, Henri van de Scheur - Sun Norway <He...@sun.com>
wrote:
>
> Hi Myrna!
>
> I understand your concern and would like to share my thoughts.
> I think a combination of 1) and 3) would be best.
> I would prefer a release now, but understand the concerns in the
> community and thereby the need for a new RC. After the 26th I will also
> start a vacation, so that would suit me fine (just in time). When we
> know that an update release will be started on in September, I guess
> that will also make it easier to accept some other critical issues in
> this RC.
>
> Thanks!
>
> Henri
>
> PS: I hope to post results of testing on 10.3.1.2 tomorrow. As far as I
> have seen so far, it looks quite good.
>
> Myrna van Lunteren wrote:
> > Hi,
> >
> > There was a discussion ensuing from DERBY-2896, which I think should
> > be a general discussion item, following mamta's check-in for a fix for
> > that critical issue.
> >
> >
> > Knut Anders Wrote:
> >> >The changes in metadata.properties will not be picked up when you
> >> upgrade from 10.3.1.x to 10.3.2.x.
> >>
> > Kathey replied:
> >> This filed as DERBY-1107 and I think is a good reason to have a new
> >> release candidate.  I think other critical issues such as DERBY-2437
> >> and the regression DERBY-2892 might be worth waiting for too if they
> >> can be fixed in short order.  I wouldn't veto a release at this point
> >> but would probably vote -0.
> >
> >
> > It seems to me that even though Kathey doesn't want to hold up the
> > release, she really doesn't want a release without this fix.
> > Which to me sounds like a new release candidate, which, as we've got a
> > vote outstanding, means holding up the release. :-)
> >
> > But Kathey's email poses some options
> > 1. I can do a fairly quick turn-around and make another release
> > candidate after Mamta backports the fix to 10.3. If I can build the
> > files tonight or tomorrow morning early, I can test, and call a vote
> > around noon, that would give us until July 26th noon (PDT) and I could
> > maybe still close the vote and hope that the maven work and web page
> > work can be finished on that day, or leave it to Rick to do that part
> > once he's back the week after.
> >
> > 2. We can wait until someone fixes DERBY-2892 for 10.3. I have not
> > heard anything positive, nor a time frame for such a fix. If a fix
> > happens before the 26th, I can generate new build files and open the
> > voting, but someone else (Rick when he's back form
> > vacation/conference?) will have to finish up the work for this
> > release.
> >
> > 3. We can wait even further until other critical issues such as
> > DERBY-2437 are fixed. I want to point out, that no has volunteered to
> > own that one at this point, so we might be waiting indefinitely. I
> > can, as I have suggested before, pick up the release work in
> > September, and we can see how far the fixes are then. Or someone else
> > can volunteer.
> >
> > Kathey, please be explicit, which 'other' issues except DERBY-2437 do
> > you think are necessary to receive a fix?
> >
> >
> > Myrna
>



-- 
Thanks,
Manjula.

Re: again, another 10.3.1. release candidate?

[Henri van de Scheur - Sun Norway <He...@Sun.COM>]

Hi Myrna!

I understand your concern and would like to share my thoughts.
I think a combination of 1) and 3) would be best.
I would prefer a release now, but understand the concerns in the 
community and thereby the need for a new RC. After the 26th I will also 
start a vacation, so that would suit me fine (just in time). When we 
know that an update release will be started on in September, I guess 
that will also make it easier to accept some other critical issues in 
this RC.

Thanks!

Henri

PS: I hope to post results of testing on 10.3.1.2 tomorrow. As far as I 
have seen so far, it looks quite good.

Myrna van Lunteren wrote:
> Hi,
>
> There was a discussion ensuing from DERBY-2896, which I think should
> be a general discussion item, following mamta's check-in for a fix for
> that critical issue.
>
>
> Knut Anders Wrote:
>> >The changes in metadata.properties will not be picked up when you 
>> upgrade from 10.3.1.x to 10.3.2.x.
>>
> Kathey replied:
>> This filed as DERBY-1107 and I think is a good reason to have a new 
>> release candidate.  I think other critical issues such as DERBY-2437 
>> and the regression DERBY-2892 might be worth waiting for too if they 
>> can be fixed in short order.  I wouldn't veto a release at this point 
>> but would probably vote -0.
>
>
> It seems to me that even though Kathey doesn't want to hold up the
> release, she really doesn't want a release without this fix.
> Which to me sounds like a new release candidate, which, as we've got a
> vote outstanding, means holding up the release. :-)
>
> But Kathey's email poses some options
> 1. I can do a fairly quick turn-around and make another release
> candidate after Mamta backports the fix to 10.3. If I can build the
> files tonight or tomorrow morning early, I can test, and call a vote
> around noon, that would give us until July 26th noon (PDT) and I could
> maybe still close the vote and hope that the maven work and web page
> work can be finished on that day, or leave it to Rick to do that part
> once he's back the week after.
>
> 2. We can wait until someone fixes DERBY-2892 for 10.3. I have not
> heard anything positive, nor a time frame for such a fix. If a fix
> happens before the 26th, I can generate new build files and open the
> voting, but someone else (Rick when he's back form
> vacation/conference?) will have to finish up the work for this
> release.
>
> 3. We can wait even further until other critical issues such as
> DERBY-2437 are fixed. I want to point out, that no has volunteered to
> own that one at this point, so we might be waiting indefinitely. I
> can, as I have suggested before, pick up the release work in
> September, and we can see how far the fixes are then. Or someone else
> can volunteer.
>
> Kathey, please be explicit, which 'other' issues except DERBY-2437 do
> you think are necessary to receive a fix?
>
>
> Myrna