Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[wtp-pmc] August 23rd telecon agenda

Welcome back to the weekly WTP PMC calls!

 

Agenda:

  • Community update and 0.7 release feedback
  • 0.7.1 status and planning
  • 1.0 release planning (see attached)
  • releng issues (see attached)
  • charter revision amendment from Mike Milinkovich
  • requirements update/planning
  • architecture update/planning
  • other items

 

I’m just returned from vacation, so apologies in advance if I’ve missed agenda items…still working through the 1000’s of emails that accrued.

 

From: wtp-pmc-bounces@xxxxxxxxxxx on behalf of Arthur Ryman [ryman@xxxxxxxxxx]
Sent: Thursday, August 11, 2005 12:52 PM
To: wtp-pmc@xxxxxxxxxxx
Subject: [wtp-pmc] WTP 1.0 and 1.5 Release Planning

I've been looking at the Eclipse schedules and have some recommendations for updating our roadmap [1].

We should update our WTP 1.0 plan to factor in the Eclipse 3.1 maintenance stream.

1. Eclipse 3.1.1 is planned for September. We should build WTP 1.0 on that.
2. Eclipse 3.1.2 is planned for January. We should release a maintenance version WTP 1.0.1 in late January. Also use that to rollu up critical bugs.

The Eclipse 3.2 plan to have a concurrent GA of the platform and projects like WTP on June 30, 2006. We should pull in our milestone dates by 2 weeks as follows:

1.5 M1: February 24, 2006 (recommend moving to February 10)
1.5 M2: April 21, 2006 (recommend moving to April 7)
1.5 M3: June 16, 2006 (recommend moving to June 2)
1.5 M4 Final: July 14, 2006 (recommend moving to June 30)

For projects that want to move to Eclipse 3.2, we should start building WTP 1.0 on both Eclipse 3.1 and 3.2. We can call the WTP 1.0 builds early versions of WTP 1.5. We should start a WTP 1.5 branch to allow work on features that are not going into WTP 1.0.

Let's put these topics on the Aug. 23 agenda.

[1] http://www.eclipse.org/webtools/development/planning/roadmap.html

Arthur Ryman,
Rational Desktop Tools Development

phone: +1-905-413-3077, TL 969-3077
assistant: +1-905-413-2411, TL 969-2411
fax: +1-905-413-4920, TL 969-4920
mobile: +1-416-939-5063, text: 4169395063@xxxxxxx
intranet: http://labweb.torolab.ibm.com/DRY6/ 
From: Naci Dai [naci.dai@xxxxxxxxxxxxx]
Sent: Tuesday, August 09, 2005 9:26 AM
To: David M Williams
Cc: Arthur Ryman; Tim Wagner
Subject: Re:
http://download.eclipse.org/webtools/maintenance/R0_7/index.php

David ,

I had the ipression that an "M" build was similar to an "R" build but was on a branch.  To me it means we need assure the quality of an "M" 
build, maybe by declaring.

Therefore I thought, having I-Build streams were appropriate.  But, I don't know how the platform does this...

Maybe we shoudl ask Sonia or John Weigand


>
> My first preference would be to stick to the way "base eclipse 
> platform does it" ... which seems to be to have maintenance builds 
> prefixed with "M" and basically every M build is an I build of 
> mainteance stream (never head) ... not sure how they distinguish 
> "released M" build.
>
> I'm only saying this assuming there's some "synergy" to re-use what 
> they've done ... if not, then your plan should be fine. I would 
> suggest, though, you check with our freindly webmaster to see if any 
> implications for mirrors, etc.
> Thanks for getting this going,
>
> David
>
>
>
>
> *Naci Dai <naci.dai@xxxxxxxxxxxxx>*
>
> 08/09/2005 04:42 AM
> Please respond to
> naci.dai
>
>
> 	
> To
> 	David M Williams/Raleigh/IBM@IBMUS
> cc
> 	Arthur Ryman <ryman@xxxxxxxxxx>, Tim Wagner <twagner@xxxxxxx> Subject
> 	http://download.eclipse.org/webtools/maintenance/R0_7/index.php
>
>
>
> 	
>
>
>
>
>
> David,
>
> Should we do a seperate drop for maintenance I-Builds? Otherwise they
> will get mixed.  The maintetnance release itself, when decalred should b
> eon the main site.  Only I, and S builds will showup here.
>
>  I prepared this drop site for it, let me know what you think.
>
> -- 
> Naci Dai,
> eteration a.s.
> Inonu cad. Sumer sok. Zitas D1-15
> Kozyatagi, Istanbul 34742
> +90 (533) 580 2393 (cell)
> +90 (216) 361 5434 (phone)
> +90 (216) 361 2034 (fax)
> http://www.eteration.com/
> mailto:nacidai@xxxxxxx
> mailto:naci@xxxxxxxxxxxxx
>
>


-- 
Naci Dai,
eteration a.s. 
Inonu cad. Sumer sok. Zitas D1-15
Kozyatagi, Istanbul 34742
+90 (533) 580 2393 (cell)
+90 (216) 361 5434 (phone)
+90 (216) 361 2034 (fax)
http://www.eteration.com/
mailto:nacidai@xxxxxxx
mailto:naci@xxxxxxxxxxxxx

Back to the top