Re: [Wtp-wst-dev] Bugs, ChangeRequests and Enhancements

[David M Williams <david_williams@xxxxxxxxxx>]

Great! As for bug fixes, you can simply
attach a patch the the bug. 
I suspect the procedure on how to do
that is outlined in Eclipse Help, 
or on the Eclilpse website, somewhere,
but basically you want to use the HEAD 
version of what ever plugin is involved,
and prepare the patch with a minimum of 
formatting changes, etc., so it contains
only changes for your bug fixes. 

It always helps to also supply a JUnit
test that demonstrates the bug (before 
patch is applied) and then demonstrates
how the patch allows the text to 
run to completion. 

Then, there is sometimes some "back
and forth" discussion in the bug if it is 
not quite right, but that's normal,
so don't be discouraged or suprised if the 
code owner has some suggestions on how
to make the patch better. 

Also, be sure you understand eclipse's
legal constraints and conditions: 
www.eclipse.org/legal. Basically, it
says contributions made via attachments 
to bugzilla are considered EPL license,
and you as the supplier of the fix 
have to, basically, confirm, by the
act of attaching, that your code you are 
attaching is your own, that you have
a right to attach it, etc. 

And, honestly, I know there have been
some attachements we do not 
respond to right away .. but, we will
... and if your patch hasn't been responded to 
after a week or two, its fine to post
a reminder, either to the bug, or this list. 

I've saved new features and extension
points to last ... .simply because they are 
exactly the same as the above, unless
its a moderately large "new feature", 
in which case you also need to fill
out a contribution questionnaire (CQ), see 
www.eclpise.org/legal. I think 500 lines
of code are given as the guideline ... 
if more than that, should have a CQ
along with the bugzilla attachment. 
And, while there's no exact guideline,
if the contribution is very large, then 
there needs to be some "promise"
that you will fix bugs later found with it, etc. 

Hope this helps .... and, don't worry,
doesn't have to be perfect the first time ... 
if somethings not quite right, we'll
still evaluate and give you feedback.

"Sannemann, Z 1903, BN" <U.Sannemann@xxxxxxxxxxxxxxx>
Sent by: wtp-wst-dev-bounces@xxxxxxxxxxx

09/22/2006 05:22 AM

Please respond to
"Web Standard Tools developer discussions." <wtp-wst-dev@xxxxxxxxxxx>

To	<wtp-wst-dev@xxxxxxxxxxx>
cc	"Shakirin, A., Z 1903, Fa. IC Consult, Bonn" <Andrei.Shakirin@xxxxxxxxxxxxxxx>
Subject	[Wtp-wst-dev] Bugs, ChangeRequests and Enhancements

I'm not sure I hit the right contact: we want to use
the WTP and Web
Standards Tools for creating our own WSDL-like service descriptions and
add new xml editors where necessary. We want to use the tools as they
are but need the extension points to regard our specific restrictions,
extensions and validations. We now get stuck on a bug that is already
known and we would like to provide the fix for testing and integration
into the next version. We also like to make suggestions for new
extension points. 
Can you tell me the correct process for these contributions?
Thanks in advance,

--
Ursula Sannemann
Deutsche Post AG
SOPSOLUTIONS(r)
D - 53250 Bonn
fon:        +49(0)228 182 19111 
fax:        +49(0)228 182 19099

_______________________________________________
wtp-wst-dev mailing list
wtp-wst-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/wtp-wst-dev