[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [dtp-dev] Reminder: DTP 1.0 M3 build tomorrow
|
Hi Hui:
I've moved that bug out to the next milestone.
Regards,
John Graham
Eclipse Data Tools Platform PMC Chair
Staff Software Engineer, Sybase, Inc.
http://dataplat.blogspot.com/
Hui.Cao@xxxxxxxxx
m
Sent by: To
dtp-dev-bounces@e DTP development mailing list
clipse.org <dtp-dev@xxxxxxxxxxx>
cc
10/27/2006 01:46 Subject
AM Re: [dtp-dev] Reminder: DTP 1.0 M3
build tomorrow
Please respond to
DTP development
mailing list
<dtp-dev@eclipse.
org>
Hi John,
The sql dev tools M2 bug is fixed. Bug 153542 can't be completed in
M3, please defer it to 1.0 RC1, thanks!
https://bugs.eclipse.org/bugs/show_bug.cgi?id=153542
Hi Anthos,
158092 is fixed. Please verify, thanks!
Best Regards!
Max ( Hui ) Cao
Sybase, Inc. Shanghai, China
Anil Samuel
<anil.samuel@xxxxxxxxxx>
Sent by: To
dtp-dev-bounces@xxxxxxxxxxx DTP development mailing
list <dtp-dev@xxxxxxxxxxx>
cc
10/27/2006 10:00 AM
Subject
Re: [dtp-dev] Reminder:
Please respond to DTP 1.0 M3 build tomorrow
DTP development mailing list
<dtp-dev@xxxxxxxxxxx>
Hi John
I should have raised this earlier; but only now noticed that this bug
(158092) is not picked for 1.0 release.
This is a feature-stopper for executing Oracle UDF.
Regards
Anthos
On 27/10/2006, at 2:41 AM, jograham@xxxxxxxxxx wrote:
>
> Just a reminder that the DTP 1.0M3 build is scheduled for tomorrow,
> 10/ 27.
> For planning purposes, committers should view midnight tonight
> (PST) as the
> build cut-off time, and that the M3 candidate build will occur
> first thing
> tomorrow morning. Once this candidate build is complete, I will
> post it to
> the usual "drops" folder and I ask that everyone plan some time
> tomorrow to
> test it. If issues of sufficient severity (as recommended by a bug
> reporter
> and approved by a PMC vote) are uncovered, we'll respin the build. We
> probably can get at most two respins tomorrow (of course, depending
> on the
> time the bugs are found) before we'd have to delay M3 declaration. If
> everything goes well, I will promote the M3 candidate to M3 status
> at 5EST
> and update the site accordingly.
>
> Committers: Please be sure to clear M3 (and still some M2!) bugs as
> necessary:
>
> 1. There are _still_ 4 bugs open against M2: 3 in Connectivity and
> 1 in
> SQL Dev. We really need to update these bugs -- are they fixed
> already?
> Should they have been deferred to a later milestone? Did we just
> forget
> about them, as they slipped through the cracks?
>
> 2. There are 6 bugs open against M3: 4 in Connectivity, 1 in Model
> Base,
> and 1 in SQL Dev.
>
> I'd like to run the M2 and M3 queries tomorrow morning, and get back
> "zaroo" for each.
>
> Regards,
> John Graham
> Eclipse Data Tools Platform PMC Chair
> Staff Software Engineer, Sybase, Inc.
> http://dataplat.blogspot.com/
>
> _______________________________________________
> dtp-dev mailing list
> dtp-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/dtp-dev
_______________________________________________
dtp-dev mailing list
dtp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/dtp-dev
_______________________________________________
dtp-dev mailing list
dtp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/dtp-dev