You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by Andrew McIntyre <mc...@gmail.com> on 2006/06/09 23:39:37 UTC
10.1.3 release - last day for checkins
Hi all,
Today is the last day for checkins for 10.1.3! Please refrain from
checking in anything for a few days while I build and test a release
candidate. I aim to have the release candidate posted by Tuesday.
It's actually ok if a couple small fixes go in over the weekend, it
just means a little more testing for me. Anything really big or
complicated to test on multiple platforms/vms and i'll probably pass
on it and build the release from the revision before such a change.
There are still four open issues left assigned to 10.1.2.5 or 10.1.3.0:
http://issues.apache.org/jira/browse/DERBY-880 - test change - punting to 10.1.4
http://issues.apache.org/jira/browse/DERBY-881 - test change - punting to 10.1.4
http://issues.apache.org/jira/browse/DERBY-1351 - intermittent test
issue - punting to 10.1.4
http://issues.apache.org/jira/browse/DERBY-1376 - can we agree on a
wording already?
But, overall a great effort, with 109 issues fixed by 30 people!
So, i have tests running on multiple platforms over the weekend, then
Monday I'll see how things went and start putting together the release
candidate if all is well. I should have it up for a vote by Tuesday,
with voting running a week as usual.
andrew
Re: 10.1.3 release - last day for checkins
Posted by Andrew McIntyre <mc...@gmail.com>.
On 6/10/06, Knut Anders Hatlen <Kn...@sun.com> wrote:
>
> I just found out that DERBY-331 has been marked with fix version
> 10.1.3, but has neither been reopened nor fixed in 10.1.3. Mayuresh
> has added a comment which says the fix merges cleanly and that
> derbyall passes. I think this fix matches the "small fixes" criterion
> since it is a simple one-line fix (plus comments and tests). It has
> been in trunk for almost a year now, so I think it should be safe to
> merge. I will reopen the issue, run derbyall, and commit if it
> succeeds and I don't hear any objections.
I'm fine with this change as long as you've run derbyall and it passed
with no unexpected results. I had noticed it earlier and was going to
investigate but I wasn't going to have time to run derbyall on it (all
my machine resources tied up at the moment), so I passed on it. Thanks
for picking it up and doing the necessary testing.
Plus now we can add Dag and Mayuresh to the list of contributors to 10.1.3. :-)
btw and fyr, latest tinderbox run from DBTG on 10.1 shows 2 failures,
but both are of the intermittent/platform-specific variety:
http://www.multinet.no/~solberg/public/Apache/TinderBox-10.1/Limited/testSummary-413354.html
My latest test run shows the intermittent DERBY-1351, in
forupdate.sql, and no other failures.
So far, so good...
andrew
Re: 10.1.3 release - last day for checkins
Posted by Knut Anders Hatlen <Kn...@Sun.COM>.
Andrew McIntyre <mc...@gmail.com> writes:
> Hi all,
>
> Today is the last day for checkins for 10.1.3! Please refrain from
> checking in anything for a few days while I build and test a release
> candidate. I aim to have the release candidate posted by Tuesday.
>
> It's actually ok if a couple small fixes go in over the weekend, it
> just means a little more testing for me. Anything really big or
> complicated to test on multiple platforms/vms and i'll probably pass
> on it and build the release from the revision before such a change.
I just found out that DERBY-331 has been marked with fix version
10.1.3, but has neither been reopened nor fixed in 10.1.3. Mayuresh
has added a comment which says the fix merges cleanly and that
derbyall passes. I think this fix matches the "small fixes" criterion
since it is a simple one-line fix (plus comments and tests). It has
been in trunk for almost a year now, so I think it should be safe to
merge. I will reopen the issue, run derbyall, and commit if it
succeeds and I don't hear any objections.
--
Knut Anders
Re: 10.1.3 release - last day for checkins
Posted by Andrew McIntyre <mc...@gmail.com>.
On 6/9/06, Kathey Marsden <km...@sbcglobal.net> wrote:
> Andrew McIntyre wrote:
>
> > It's actually ok if a couple small fixes go in over the weekend.
>
> Would it be ok to commit DERBY-1327. It has a bunch of files but there
> is no logic change. Just removal of an unneeded parameter. Here is what
> Mamta says about it:
>
> "This parameter is always equal to (parameter named autoincInc != 0). In
> my patch , I have removed the autoinc parameter and inside the
> constructors, I use (parameter named autoincInc != 0) instead of relying
> on autoinc."
>
> Cleaning up the code prevents a JIT issue from being triggered.
Yes, it's fine if this goes in over the weekend, since its a simple
change. Please try to have it in by Monday, 8AM Pacfic time at the
absolute latest. Sooner is better than later, since I will need to run
additional tests related to the change.
Thanks,
andrew
Re: 10.1.3 release - last day for checkins
Posted by Kathey Marsden <km...@sbcglobal.net>.
Andrew McIntyre wrote:
> It's actually ok if a couple small fixes go in over the weekend.
Would it be ok to commit DERBY-1327. It has a bunch of files but there
is no logic change. Just removal of an unneeded parameter. Here is what
Mamta says about it:
"This parameter is always equal to (parameter named autoincInc != 0). In
my patch , I have removed the autoinc parameter and inside the
constructors, I use (parameter named autoincInc != 0) instead of relying
on autoinc."
Cleaning up the code prevents a JIT issue from being triggered.
Kathey
Re: 10.1.3 release - last day for checkins
Posted by Andrew McIntyre <mc...@gmail.com>.
On 6/9/06, Rajesh Kartha <ka...@gmail.com> wrote:
>
> I think the voting should last for atleast 2 weeks, this will give
> enough time for everyone in the community to do their respective
> testing on various platform/jvm combinations.
Sure, I can extend the voting to two weeks if those doing testing need
the time. Assuming all goes well and I post the release candidate on
the 13th, and there are no further problems, I will now close voting
on June 27 at the same time the vote is posted on the 13th.
andrew
Re: 10.1.3 release - last day for checkins
Posted by Rajesh Kartha <ka...@gmail.com>.
So, i have tests running on multiple platforms over the weekend, then
> Monday I'll see how things went and start putting together the release
> candidate if all is well. I should have it up for a vote by Tuesday,
> with voting running a week as usual.
>
> andrew
>
I think the voting should last for atleast 2 weeks, this will give
enough time for everyone in the community to do their respective
testing on various platform/jvm combinations.
Regards,
Rajesh