[dtp-dev] DTP 1.0RC2 candidate available / bug status

[jograham@xxxxxxxxxx]

A candidate (12/15 nightly) for DTP 1.0RC2 is now available on the download
site. Currently there are 5 (non doc, non test) bugs open for DTP 1.0. Of
these, only two, in my opinion, are valid candidates for 1.0:

> 166637 (Driver definition not saved)
> 168227 (NPE in table data editor)

I also feel that neither of these blocks the RC2 promotion tonight, and I
currently believe that neither of these ultimately would delay a 1.0
release the week of 12/18. That is, while it would be nice to have these
fixed in time for 1.0, the first represents a fairly obscure scenario that
causes some inconvenience, but can be readily recovered from. The second
represents additional functionality for DTP 1.0, and could be postponed to
a later release.

Of course, these are just my suggestions: ultimately, it will be up to the
community to petition the PMC to postpone the RC2 promotion and/or the
release date until certain items can be addressed. The PMC will consider
these petitions as normal, and decide based on the overall DTP 1.0 picture.

Finally, note that today's build could -- in theory -- be the last for DTP
1.0. Technically (by the endgame plan), no other builds are planned, and
any changes are tightly constrained. Given the bugs cited above, however, I
expect that there will be at least one more build for DTP 1.0. Note three
very important points:

1. I will build against the RC2 tag by default. I will build against HEAD
only for those plug-ins that have PMC approved changes to them. So, if you
do not get PMC approval for a change, or you do not tell me that a change
is complete, it will not be picked up in DTP build from here until 1.0
release.

2. The last possible build date to make a 12/22 release (assuming we pass
the release review) is Thursday, 12/21. We need to do sanity checks against
any final build, and allow time for mirror propagation before announcing a
1.0 release. This means that only 4 more builds are available. I would urge
work to be completed as soon as possible, so we can have the maximum number
of chances to test and address any further issues before the build window
closes.

3. Most of the DTP staff will not be available the from 12/23 -- 1/2.
Therefore, if we do not release on 12/22 at latest (because of bugs or
issues raised in the release review), we will have to suspend activity
until after 1/2. In this case, we will post the last release candidate for
community testing and consumption, and deal with the release in early
January.

Regards,
John Graham
Eclipse Data Tools Platform PMC Chair
Staff Software Engineer, Sybase, Inc.
http://dataplat.blogspot.com/