[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [wtp-dev] clarification needed about bug submitting process
- From: Mukul Gandhi <gandhi.mukul@xxxxxxxxx>
- Date: Fri, 1 May 2009 10:23:28 +0530
- Delivered-to: firstname.lastname@example.org
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type:content-transfer-encoding; b=MdgK01ylb7hZz1+VSyWxzfXyjc10acODouYN+Ffy4ccpOEUHWTl/cXiH8boZFgLl4a pgjdoY206kvqI8/QOLI2ruYLvvD4uLgOhlZcIBagOzIZWUOqRkeBShKchN5kjntOlTvh BuF+wpgazxqYeMISGPIiShbc4YxNKXFaj4Kpo=
Thanks, for your reply.
I wish to know the tentative plans of WTP 3.2 development (M1 and
onwards) after Eclipse GA is released. Will WTP 3.2 be targeted to be
used with Eclipse GA?
On Fri, May 1, 2009 at 9:43 AM, David M Williams
> 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
> The long answer is documented in our ramp down plan.
> 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.