Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [ptp-dev] 2.0 Release Planning
You can commit everything except his contribution. You'll need to open a PTP bug with just his contribution as an attachment if possible. Let me know when you've done it and I'll start the IP process.

Greg

On Mar 5, 2008, at 5:21 PM, Craig Rasmussen wrote:

Matt's was less than 250 to the code I'll commit.  Brian's was more.  What is the process for Eclipse legal?  Should I commit first?

Craig

On Mar 5, 2008, at 1:05 PM, Greg Watson wrote:

No, it won't interfere with the release, so anytime is ok.  If Brian and Matt's contributions were greater than 250 lines of code (each), then their work will need to be approved by Eclipse legal. Yours and Chris's can be committed any time.

Regards,

Greg


On Mar 5, 2008, at 10:40 AM, Craig Rasmussen wrote:

Greg,

I'm tagging and releasing the latest Fortran parser work we've done and would like to commit it to the PTP repository sometime soon.  I assume we should wait until after the release?  As far as IP issues go, we've had contributions from Brian Rasmussen (a former Post Doc at LANL) and Chris Rickett and Matt Sottile (former TSMs at LANL).

Cheers,
Craig

On Mar 4, 2008, at 11:10 AM, Greg Watson wrote:

Wyatt,

Thanks for the info. Would you have any objections if we changed the extension points to:

org.eclipse.ptp.perf.dataManagers
org.eclipse.ptp.perf.workflows
org.eclipse.ptp.perf.configurationTabs

If an extension point can define multiple extensions, then it should be plural. Also, the extra 'perf' seems redundant.

Thanks,

Greg

On Mar 4, 2008, at 8:22 AM, wspear wrote:

I will try to add some performance related items to the test plan in the next few days.

-Wyatt

For the Performance Framework:

- a brief list of the major features
1: Adds a performance-analysis launch configuration system, analogous to the launch and debug configurations
2: Allows specification of performance analysis operations via an external, user-created XML file, extensions to the basic performance framework or a combination of the two
2a: Specification of performance analysis run-time build, allows rebuilding of projects with performance-analysis specific compiler commands
2b: Composed execution, allows specification of multiple composed applications, for performance analysis that requires the program being analyzed to be passed to another program as an argument
2c: Post-execution analysis, allows execution of a series of applications on generated performance data
3: XML GUI generator, allows specification of a GUI for selecting CLI-based performance analysis tool options via an XML file
4: TAU performance analysis tool plugin, extends the performance framework with capabilities specific to the TAU performance analysis system, including selective instrumentation, PAPI performance counter selection, profile storage and visualization using perfdmf and paraprof respectively.

- a brief list of the documentation and other non-code aspects
Done:  Example performance tool workflow/GUI-generation xml file
ToDo: Comprehensive explanation of tool xml workflow/gui definition format
ToDo: Overview of performance framework usage/interface

- a brief list of non-provisional API's and extension points
Extension Points
perfdatamanager:  Allows the developer to define action to be taken by Eclipse after performance data is generated
perfworkflow:  Allows the developer to include a tool workflow xml file within an extension
perfconfigurationtab:  Allows the developer to define a custom tab for performance tool configuration (supplementing the GUIs that can be defined by the xml gui generator)


On Mon, Mar 3, 2008 at 3:02 PM, Beth Tibbitts <tibbitts@xxxxxxxxxx> wrote:
Info for PLDT 2.0:

- a brief list of the major features
PLDT 2.0
-- adds a new single-menu UI for PLDT analysis features, simplifying the
editor toolbar
-- MPI Barrier Analysis detects possible deadlocks in MPI applications
-- New project wizards and templates for MPI and OpenMP projects
-- Welcome page addition includes pointers to PLDT information (PTP core
too)



- a brief list of the documentation and other non-code aspects

-- PLDT help includes instructions and tutorial for using the major
features.
-- Welcome page addition announces PLDT content and guides the user to
help/tutorial


- a brief list of non-provisional API's and extension points
None.

- anything else you want in the review
Nothing else I can think of.


I have updated the test plan on the wiki somewhat.


..Beth

Beth Tibbitts  (859) 243-4981  (TL 545-4981)
High Productivity Tools / Parallel Tools  http://eclipse.org/ptp
IBM T.J.Watson Research Center
Mailing Address:  IBM Corp., 745 West New Circle Road, Lexington, KY 40511



            Greg Watson
            <g.watson@compute
            r.org>                                                     To
            Sent by:                  Parallel Tools Platform general
            ptp-dev-bounces@e         developers <ptp-dev@xxxxxxxxxxx>
            clipse.org                                                 cc

                                                                  Subject
            02/27/08 08:56 PM         ** [ptp-dev] 2.0 Release Planning


            Please respond to
             Parallel Tools
            Platform general
               developers
            <ptp-dev@eclipse.
                  org>






I think we're now in a position to finalize the 2.0 release, so I'd
like to propose the following timetable:

3/05/08 Release review documentation and legal review completed
3/12/08 PTP 2.0 release review
3/17/08 Final pre-release build
3/17/08 Start testing period
3/24/08 First release respin (if required)
3/28/08 End testing period
3/28/08 Second release respin (if required)
3/31/08 2.0 target release date

Unfortunately the first week of testing coincides with EclipseCon, but
I don't think there's anything we can do about that. Perhaps we can
have an informal test-a-thon at EclipseCon?

To meet this timetable, the following is required from each major
component provider:

1. By 3/5/08, provide:

- a brief list of the major features
- a brief list of the documentation and other non-code aspects
- a brief list of non-provisional API's and extension points
- anything else you want in the review

2. Update the 2.0 test plan prior to 3/17/08. The test plan is here:
http://wiki.eclipse.org/PTP/testing/2.x

3. Undertake some testing during the testing period.

The major component providers are:

Greg Watson - PTP Core
Beth Tibbitts - PLDT
Dave Wootton - PE/LL
Daniel Ferber - Remote Tools
Wyatt Spear - Performance Tools Framework/TAU

Please let me know if this is achievable, or if we need to reschedule
the release.

Thanks,

Greg
_______________________________________________
ptp-dev mailing list
ptp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/ptp-dev


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


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

_______________________________________________
ptp-dev mailing list

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

_______________________________________________
ptp-dev mailing list

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

Back to the top