[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [wtp-dev] clarification needed about bug submitting process
|
The short answer is that yes, bugs can still go in between M7 and the
Release in June. But there is an ever increasing amount of review
required.
The long answer is documented in our ramp down plan.
http://wiki.eclipse.org/WTP_3.1_Ramp_down_Plan_for_Galileo
If you are asking if they will go into CVS, but not be released for a
build, that's something we have no project-wide formal policy on. I
normally encourage teams not to do it ... at least in HEAD ... in case
some bug is discovered that requires a fast fix, then HEAD is ready to go.
Some teams do "post release" work early in some temporary side branch.
HTH
From:
Mukul Gandhi <gandhi.mukul@xxxxxxxxx>
To:
"General discussion of project-wide or architectural issues."
<wtp-dev@xxxxxxxxxxx>
Date:
04/30/2009 11:14 PM
Subject:
[wtp-dev] clarification needed about bug submitting process
Sent by:
wtp-dev-bounces@xxxxxxxxxxx
Hi all,
I was reading the project plan for WTP 3.1 source editing release,
at
http://www.eclipse.org/projects/project-plan.php?projectid=webtools.sourceediting
.
I have following questions please.
Some of the XPath 2.0 fixes I submitted will go to, WTP M7. Thanks for the
same.
Can I submit few more bug fixes between WTP 3.1 M7 and GA, and does
the process allow that they be committed to the project CVS server
between this duration (of course, only if patches pass the review)?
Or, if I submit any bug fixes now (between WTP 3.1 M7 and GA), will
they sit idle till GA is released?
--
Regards,
Mukul Gandhi
_______________________________________________
wtp-dev mailing list
wtp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/wtp-dev
