[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
RE: Fw: [eclipse.org-planning-council] September 20 Conference ca ll agenda
|
The CDT is in an interesting situation. We are still targeting a 6 month
release cycle. We have another Eclipse 3.1.x based release scheduled for
Jan/Feb. We'll be ready to hop on the 3.2 train shortly after that. We have
generally needed 2-4 weeks to adopt a platform milestone build.
That's all I have for now. We'll discuss this further at the CDT developers'
conference later this month.
Cheers,
Doug Schaefer
Senior Software Developer
QNX Software Systems
> -----Original Message-----
> From: eclipse.org-planning-council-bounces@xxxxxxxxxxx
> [mailto:eclipse.org-planning-council-bounces@xxxxxxxxxxx] On Behalf Of
> David J. Orme
> Sent: October 3, 2005 9:46 AM
> To: eclipse.org-planning-council
> Subject: Re: Fw: [eclipse.org-planning-council] September 20 Conference
> call agenda
>
> Nobody asked, but I didn't say either. VE is also on the release train.
>
> Dave
>
> jograham@xxxxxxxxxx wrote:
>
> >DTP is committed to being on the release train.
> >
> >Regards,
> >John Graham
> >Staff Software Engineer
> >Sybase, Inc.
> >telephone: (978) 287-1634 (GMT - 5)
> >e-mail: john.graham@xxxxxxxxxx
> >
> >
> >
> >
> > Paula Cox
> > <paulacox@xxxxxx.
> > com>
> To
> > Sent by: "eclipse.org-planning-council"
> > eclipse.org-plann <eclipse.org-planning-
> council@eclip
> > ing-council-bounc se.org>
> > es@xxxxxxxxxxx
> cc
> >
> >
> Subject
> > 09/30/2005 05:50 Fw: [eclipse.org-planning-council]
> > PM September 20 Conference call
> agenda
> >
> >
> > Please respond to
> > "eclipse.org-plan
> > ning-council"
> > <eclipse.org-plan
> > ning-council@ecli
> > pse.org>
> >
> >
> >
> >
> >
> >
> >
> >Hello, Can I ask, where do we stand on this? Below we have heard from
> >BIRT and TPTP.
> >
> >I haven't seen anything from DTP - are they committed to be on the train?
> >
> >Also, WTP asked
> > >>is there a final version of the calendar leading up to the
> train
> >release available?
> >but I hadn't seen an answer on that. The 3.2 release plan,
> >http://www.eclipse.org/eclipse/development/eclipse_project_plan_3_2.html,
> >still only mentions milestones up to the end of December.
> >
> >Any updates would be appreciated.
> >
> >Thanks,
> >Paula Cox
> >Operations Manager, IBM Eclipse Review Board
> >IBM Eclipse SDK, Project Management
> >919-254-6686 tl/444-6686
> >fax: 919-254-4183 t/l 444-4183
> >paulacox@xxxxxxxxxx
> >
> >----- Forwarded by Paula Cox/Raleigh/IBM on 09/30/2005 05:37 PM -----
> >
> >
> >
> > "Wenfeng Li" <wli@xxxxxxxxxxx>
> >
> > Sent by:
> To
> > eclipse.org-planning-council-b "eclipse.org-planning-
> council
> > ounces@xxxxxxxxxxx "
> > <eclipse.org-planning-
> council
> > @eclipse.org>
> > 09/21/2005 05:12 PM
> cc
> >
> >
> Subject
> > Please respond to RE:
> > "eclipse.org-planning-council [eclipse.org-planning-
> council
> > " ] September 20 Confernce
> call
> > agenda
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >BIRT project is on schedule to synch up with the release train as well...
> >Following is our milestone plan to the end of this year. The plan is to
> >synch up on 11/21 BIRT M3, 2 weeks after the platform milestone build.
> >
> >- Friday, September 16, 2005 BIRT 2.0 M1
> >- Monday, October 24, 2005 BIRT 2.0 M2
> >- Monday, November 21, 2005 BIRT 2.0 M3
> >- Monday, December 5, 2005 BIRT 2.0 Release Candidate
> >
> >
> >- Monday, Tentative December 30, 2005 BIRT 2.0 depends on release review
> >
> >Regards,
> >
> >Wenfeng
> >-----Original Message-----
> >From: eclipse.org-planning-council-bounces@xxxxxxxxxxx
> >[mailto:eclipse.org-planning-council-bounces@xxxxxxxxxxx]On Behalf Of
> >Thessin, Tyler
> >Sent: Wednesday, September 21, 2005 12:47 AM
> >To: eclipse.org-planning-council
> >Subject: RE: [eclipse.org-planning-council] September 20 Confernce call
> >agenda
> >
> >I wasn't able to attend the PC this week due to a conflict.
> >
> >Re the release train topic in the proposed agenda - Choo choo...
> >
> >Re TPTP alignment with the release train, I have action to formally
> >indicate the TPTP will board the train - please consider that done.
> >
> >Our specific plans to date (based on what we currently know) are as
> >follows:
> >
> >
> >
> >|---------------+---+----------------------------------------------------
> |
> >| What | Wh| Why
> |
> >| | en|
> |
> >| | |
> |
> >|---------------+---+----------------------------------------------------
> |
> >| EP 3.2 M2 | Se|
> |
> >| | pt|
> |
> >| | 23|
> |
> >| | |
> |
> >|---------------+---+----------------------------------------------------
> |
> >| TPTP 4.1 I2 | Oc| Build of current TPTP 4.1 functionality in
> |
> >| Candidate | t | preparation for first formal build on EP 3.2 Nov
> 18|
> >| (Test Build on| 17|
> |
> >| EP 3.2 M2) | |
> |
> >|---------------+---+----------------------------------------------------
> |
> >| TPTP 4.1 GA | No| Next major TPTP release
> |
> >| (Available on | v |
> |
> >| EP 3.1.1) | 11|
> |
> >| | |
> |
> >|---------------+---+----------------------------------------------------
> |
> >| | |
> |
> >|---------------+---+----------------------------------------------------
> |
> >| EP 3.2 M3 | No|
> |
> >| | v |
> |
> >| | 4 |
> |
> >|---------------+---+----------------------------------------------------
> |
> >| TPTP 4.2 "M3" | No| First formal TPTP build on EP 3.2 (Functionally
> |
> >| (Available on | v | equivalent to TPTP 4.1 GA)
> |
> >| EP 3.2 M3) | 18|
> |
> >| | |
> |
> >|---------------+---+----------------------------------------------------
> |
> >| EP 3.2 M4 | De|
> |
> >| | c |
> |
> >| | 16|
> |
> >| | |
> |
> >|---------------+---+----------------------------------------------------
> |
> >| TPTP 4.2 "M3" | ~D| Second formal TPTP build on EP 3.2 (Functionally
> |
> >| (Available on | ec| equivalent to TPTP 4.1 GA)
> |
> >| EP 3.2 M3) | 17|
> |
> >| | |
> |
> >|---------------+---+----------------------------------------------------
> |
> >| TPTP 4.2 | Ja| We have "down-time" between Nov 11-Jan 6
> |
> >| Formal start | n |
> |
> >| of development| 9 |
> |
> >| | |
> |
> >|---------------+---+----------------------------------------------------
> |
> >| EP 3.2 RC0 | Ap|
> |
> >| | r |
> |
> >| | 1 |
> |
> >|---------------+---+----------------------------------------------------
> |
> >| TPTP 4.2 I2 | Ap| We'll plan alignment with EP milestones during
> this|
> >| (Available on | r | period when such are published
> |
> >| EP 3.2 RC0) | 14|
> |
> >| | |
> |
> >|---------------+---+----------------------------------------------------
> |
> >| TPTP 4.2 I3 | Ju| Final TPTP feature development iteration to be
> |
> >| (Available on | n | aligned as appropriate with EP milestones during
> |
> >| EP 3.2 RC?) | 2 | this period when published.
> |
> >|---------------+---+----------------------------------------------------
> |
> >| TPTP 4.2 GA | ~J| We'll plan alignment with EP milestones during
> this|
> >| (Available on | un| period when such are published - we're generally
> |
> >| EP 3.2 GA & | 30| expecting to be in frequent build/test mode toward
> |
> >| EMF GA) | | ~simultaneous closure with EP
> |
> >|---------------+---+----------------------------------------------------
> |
> >
> >
> >
> >
> >Thanks,
> >
> >--tyler
> >
> >
> >
> >
> >From: eclipse.org-planning-council-bounces@xxxxxxxxxxx
> >[mailto:eclipse.org-planning-council-bounces@xxxxxxxxxxx] On Behalf Of
> >Bjorn Freeman-Benson
> >Sent: Tuesday, September 20, 2005 7:01 AM
> >To: eclipse.org-planning-council
> >Subject: [eclipse.org-planning-council] September 20 Confernce call
> agenda
> >
> > 613.287.8000
> >or 866.362.7064
> >passcode 874551#
> >
> >8am PDT, 11am EDT, 5pm CET
> >
> >Actually, I don't have much of an agenda for today's first resumed
> monthly
> >conference call so it might be very short.
> > We could discuss the conference call timing, although that might be
> > difficult because the people most interested in changing the time
> are
> > those that cannot make today's call :-)
> > I'd also like to hear from BIRT, DTP, TPTP, WTP, and the Tools
> > projects about the status of sync'ing their project plan with the
> > release train project plan.
> > And a reminder that everyone is going to freshen their web content
> > (at the very least, remove / annotate dead information) by the end
> of
> > the month.
> >--
> >
> >
> >
> > Bjorn
> > Freeman-Benson
> > Technical Director,
> > Open Source Process
> > and Infrastructure
> > Eclipse Foundation
> >
> > voice: 971-327-7323 (PDT, UTC-7)
> >
> > email: bjorn.freeman-benson@xxxxxxxxxxx
> >
> >
> >
> >
> > _______________________________________________
> >eclipse.org-planning-council mailing list
> >eclipse.org-planning-council@xxxxxxxxxxx
> >https://dev.eclipse.org/mailman/listinfo/eclipse.org-planning-council
> >_______________________________________________
> >eclipse.org-planning-council mailing list
> >eclipse.org-planning-council@xxxxxxxxxxx
> >https://dev.eclipse.org/mailman/listinfo/eclipse.org-planning-council
> >
> >
> >------------------------------------------------------------------------
> >
> >_______________________________________________
> >eclipse.org-planning-council mailing list
> >eclipse.org-planning-council@xxxxxxxxxxx
> >https://dev.eclipse.org/mailman/listinfo/eclipse.org-planning-council
> >
> >
>
>
> --
> Coconut Palm Software http://www.coconut-palm-software.com
> Objects are here to stay http://www.db4o.com
>
> PGP Public Key (for confidential communications):
> http://www.coconut-palm-software.com/~djo/public_key.txt
>
> _______________________________________________
> eclipse.org-planning-council mailing list
> eclipse.org-planning-council@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/eclipse.org-planning-council
