Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 332668 - Photran needs to be tested with 4.1 SDK compatibility layer
Summary: Photran needs to be tested with 4.1 SDK compatibility layer
Status: RESOLVED FIXED
Alias: None
Product: PTP
Classification: Tools
Component: Photran.For Internal Use (show other bugs)
Version: 6.0   Edit
Hardware: All All
: P4 normal (vote)
Target Milestone: ---   Edit
Assignee: Jeffrey Overbey CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 340437
  Show dependency tree
 
Reported: 2010-12-15 13:44 EST by Jeffrey Overbey CLA
Modified: 2011-03-18 11:11 EDT (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jeffrey Overbey CLA 2010-12-15 13:44:31 EST
[cross-project-issues-dev] Please test your project using the 4.1 SDK compatibility layer (in M4)

from	Eric Moffatt <emoffatt@ca.ibm.com>
sender-time	Sent at 1:46 PM (GMT-05:00). Current time there: 1:43 PM. &#9990;
reply-to	Cross project issues <cross-project-issues-dev@eclipse.org>
to	cross-project-issues-dev@eclipse.org
date	Tue, Nov 23, 2010 at 1:46 PM

The Platform team has already taken a few of the products (notably JDT, CDT and Mylyn) through the testing exercise. This input has been very valuable to us and has allowed us to get to the point where the SDK is generally testable. One goal was to minimize the cost to you  of testing your component in the 4.1 SDK compatibility layer. See Chris Recoskie's excellent blog on our testing efforts for CDT. 

We need your help in order to be successful. We've taken the code to a state where we are confident that we cover most normal uses of our api but it's impossible for us to test the projects; we simply don't know enough about them to be able to know when something is missing or otherwise not working correctly. The testing should only take ~2-3 hours, depending on how complex the UI for your project is.

I'm more than willing to spend that time on the phone with anybody who is testing a component (as I did with Chris). If you're encountering issues that are preventing you from testing please  contact me directly and I'll see if I can help. 

The target for this testing is within the M4 milestone, waiting until M5 risks that we run out of time to fix a reported defect. If you wish you can pick up 4.1 SDK M3 here and get a head start but it might be best to have me work with you so that we can identify whether or not a particular issue has already been addressed (i.e. I'll run the same scenario against the more current code). 

I've opened Bug 330957 to help track the testing effort; Please comment there whether or not you intend to participate in the testing (even the negatives will be valuable input...;-). If you're going to participate and want me to assist then indicate this on the bug and we'll schedule a time... Once I've received sufficient feedback on the defect I'll be creating a 4.1 SDK 'scorecard' on the E4 wiki to track the ongoing progress. 

Feel free to contact me directly by email or via IRC at #eclipse-e4 if you have any  questions or concerns... 

Remember, you get out what you put in (and thanks in advance), 
Eric 

_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
Comment 1 Jeffrey Overbey CLA 2011-03-18 00:42:12 EDT
Started testing.  See today's post on photran-dev 3/17/2011
Comment 2 Jeffrey Overbey CLA 2011-03-18 11:11:53 EDT
Filed Bug 340437 - Photran's dynamic "Refactor" menu does not display correctly in e4

Closing this bug since preliminary Photran testing is complete.