[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [eclipse.org-planning-council] Re: [cross-project-issues-dev] Question about a DTP build later today and the release train...
However, the schedule does allow for an RC5 [1], so there's still next week to get it fixed, then to rename your RC5 bits to R on final server freeze day [2].

[1]http://wiki.eclipse.org/Ganymede#Milestones_and_Release_Candidates
[2]http://wiki.eclipse.org/Ganymede_Final_Daze

Nick

On Thu, Jun 12, 2008 at 10:44 AM, <brian.fitzpatrick@xxxxxxxxxx> wrote:

Definitely not a stop ship bug. The ship will keep on chugging without it.

Brian Fitzpatrick
Eclipse Data Tools Platform PMC Chair
Eclipse Data Tools Platform Connectivity Team Lead
Senior Software Engineer, Sybase, Inc.


Bjorn Freeman-Benson <bjorn.freeman-benson@xxxxxxxxxxx>
Sent by: eclipse.org-planning-council-bounces@xxxxxxxxxxx

06/12/2008 08:41 AM

Please respond to
"eclipse.org-planning-council"        <eclipse.org-planning-council@xxxxxxxxxxx>
To
Cross project issues <cross-project-issues-dev@xxxxxxxxxxx>
cc
"eclipse.org-planning-council" <eclipse.org-planning-council@xxxxxxxxxxx>
Subject
[eclipse.org-planning-council] Re: [cross-project-issues-dev] Question about a DTP build later today and the release train...





Brian,
Here's my opinion: "is a documentation bug a stop ship bug?"  If so, then I would vote +1 for a respin. However, since I personally can't see how a documentation bug is a stop ship, you'll have to convince me that it's important; otherwise I'll vote -1. My argument is that at some point we have to stop changing the bits. RC4 (now) is that point.

- Bjorn
We have an extension schema-related documentation bug that would require a respin of the DTP 1.6 (Ganymede) RC4 build to create a RC4a.

--

[end of message] _______________________________________________
eclipse.org-planning-council mailing list
eclipse.org-planning-council@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/eclipse.org-planning-council

IMPORTANT: Membership in this list is generated by processes internal to the Eclipse Foundation.  To be permanently removed from this list, you must contact emo@xxxxxxxxxxx to request removal.

_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev