Re: [wtp-pmc] Weekend status on RC3 preparation

[David M Williams <david_williams@xxxxxxxxxx>]

Here's my take (and vote) on potential
reason's to create an RC4.  
I'm drawing a pretty hard line (all
-1)  ... but am open to others views, new data, and the decision of
the PMC. 


Mentioned in Tim's attached note: 

120109
blo P2 PC deboer@xxxxxxxxxx ASSI 1.0 M10 Unable to download Geronimo 
-1 Its a tiny fix, plugin.xml only,
but 
        1)
for demo, not product per se (and for demo, the client can fix his own
plugin.xml file!). 
        2)
I don't think we really have the right solution in this whole area ...
* our code* should not be naming download sites for any servers. 
         
 (there should be a central download site, or something, that anyone
could freely participate in). 
      3) The proposed
"fix" (workaround) will remain "wrong" even when the
update site is fixed. 
120003
enh P2 PC deboer@xxxxxxxxxx ASSI 1.0.1 Neither Add or Remove utility project
to dynamic web project set server state to republish

-1   Tim recommends it, but, the
originator did agree it could be postponed to 1.0.1 ... so, in the spirit
of shutting down... let's honor the originators opinion? 

120266  cri     wst.vali
       1.0 M10 Importing an existing web project into
a clean workspace locks validator
-1   a work around exists, and,
I'm not sure proposed fix really fixes the problem (or, if we really know
what problem is). 

120244   Cannot install other facets
from within an install delegate.
-1  It is bad we ever deadlock,
but I think Kosta has adequately explained this deadlock results from "misuse"
of intended use. 
      I suspect we'll
hear soon if originator disagrees, or feels they can not use facets if
they can not use in the way they were trying. 


Others that need triage or may come
up: 

Hot List with M10 or unspecified targets

119939  maj     jst.serv
       ---     Error when publishing Dynamic
web app to Websphere 6
-1  One part of defect was agreed
to move to 1.0.1, and I believe other part is already covered by other
bugs deferred to 1.0.1
      (i.e. changing
context root) but maybe others can clarify my questions in that bugzilla.



Blocker or critical with M10 or unspecified
target

120280  cri     jst.j2ee
       ---     "Could not publish to
the server" on wtp 1.0rc2
-1  not sure how many would see
this? [may be most likely to need a re-build]

120232  cri     wst.wsdl
       ---     Web Services Generate Client
NPE in WSDL2JavaCommand.createTempDir()
-1 may be hard to reproduce, or "install
specific" .. and probably not valid "critical".

"Tim Wagner" <twagner@xxxxxxx>
Sent by: wtp-pmc-bounces@xxxxxxxxxxx

12/11/2005 03:00 PM

Please respond to
"WTP PMC communications (including coordination, announcements,  and Group discussions)"

To	"WTP PMC communications (including coordination, announcements,  and Group discussions)" <wtp-pmc@xxxxxxxxxxx>
cc
Subject	[wtp-pmc] Weekend status on RC3 preparation

Some consolidated status from weekend progress
on RC3. Of most concern are the unknown/not-in-RC3 bugs, which includes
Naci’s validation issue (120266). Even assuming an RC3 ready by Monday
AM, it looks like we’ll have to make a call on an RC4 (which would necessarily
push out the release date) for inclusion of any of these issues.
 
Fixed, Awaiting PMC Approval for RC3:
 
120109
blo P2 PC deboer@xxxxxxxxxx ASSI 1.0 M10 Unable to download Geronimo server
Dynamic support for downloading the Geronimo server adapter is failing
because the update manager API we're using does not handle mirrors correctly.
The quick fix for 1.0 is to change the update manager URL to point directly
to one of the mirrors. 

120003
enh P2 PC deboer@xxxxxxxxxx ASSI 1.0.1 Neither Add or Remove utility project
to dynamic web project set server state to republish
I had started to investigate this bug before Arthur cleverly convinced
the originator to defer to 1.0.1. However, while investigating and fixing
this I found a case where servers were not firing publish state changes
correct and another where the Servers view was not updating correctly.
As a result, adopter plugins can get out of sync with a server and end
users may interpet this as instability or bugs in the publish detection.
Although this isn't blocking, I beleive this fix will improve stability
and avoid a number of ugly publishing issues.
 
(+1 on both from me – both are “hot list”
entries.)
 
 
Status Unknown / RC Unplanned:
 
https://bugs.eclipse.org/bugs/show_bug.cgi?id=120244
 
117755
Extension point documentation missing for many plug-ins 
117966 Update org.eclipse.jst.server.ui.doc.user
and org.eclipse.wst.server.ui.doc.user
 
https://bugs.eclipse.org/bugs/show_bug.cgi?id=120266
 
 
Released for RC3:
 
119769
cri P2 PC deboer@xxxxxxxxxx ASSI 1.0 M10 No modification stamp change in
Utility project 
110455
enh P2 PC deboer@xxxxxxxxxx ASSI 1.0 M10 List Downloadable Server Runtimes
118727
blo P2 PC deboer@xxxxxxxxxx ASSI 1.0 M10 Unable to set web module path
in server document
 
116539
missing some infopop documentation (for SSE related function)
117755
Extension point documentation missing for many plug-ins      <--
I'm waiting on one last fix for this bug
119945
update html file on creating session bean
120022
Please update org.eclipse.wst.server.ui.infopop and org.eclipse.jst.server.ui.infopop_______________________________________________
wtp-pmc mailing list
wtp-pmc@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/wtp-pmc