Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [eclipse-dev] Planning Meeting Notes - 7 Dec 2011

Yes we are actually creating that report right now, it just needs to be pushed into an email. See discussion in bug:

https://bugs.eclipse.org/bugs/show_bug.cgi?id=364078

For the curious, here is what the report currently looks like for this morning's 8am EST build. We would likely want to improve the format of the report once we get it in place.

The build contains the following changes:
+ Bug 363930 - Add org.eclipse.equinox.http.servlet.tests to rt.equinox.bundles (FIXED)
+ Bug 365073 - Patcher#applyAll doesn't expect null progress monitor (FIXED)
+ Bug 365348 - Team.cvs not shipping extension point schemas in plugins (FIXED)
+ Bug 365654 - version of org.eclipse.equinox.server.jetty feature should be incremented in 3.8 stream builds (FIXED)
+ Bug 365661 - PDE wizard doesn't properly set the API Tools nature and builder when creating a new plug-in project (FIXED)
+ Bug 365720 - NPE in ViewerComparator.sort(ViewerComparator.java:195) (FIXED)

The following projects have changed:
org.eclipse.compare
org.eclipse.core.net
org.eclipse.equinox.http.servlet.tests
org.eclipse.equinox.p2.artifact.repository
org.eclipse.equinox.p2.tests
org.eclipse.equinox.server.jetty
org.eclipse.jface
org.eclipse.jsch.core
org.eclipse.pde.ui
org.eclipse.team.cvs.core



Thomas Watson <tjwatson@xxxxxxxxxx>
Sent by: eclipse-dev-bounces@xxxxxxxxxxx

12/07/2011 11:29 AM

Please respond to
"General development mailing list of the Eclipse project."        <eclipse-dev@xxxxxxxxxxx>

To
"General development mailing list of the Eclipse project." <eclipse-dev@xxxxxxxxxxx>
cc
Subject
Re: [eclipse-dev] Planning Meeting Notes - 7 Dec 2011





I had meant to bring this up during the call today for discussion:

When merging master into integration branch for the I-Builds is there a
recommended way to generate the releng notes that we used to get with the
CVS releng tools and the previous git report scripts?

Should the build simply generate this report automatically for each
I-Build?

Tom




                                                                                                                                 
 From:       Curtis Windatt <Curtis_Windatt@xxxxxxxxxx>                                                                          
                                                                                                                                 
 To:         eclipse-dev@xxxxxxxxxxx,                                                                                            
                                                                                                                                 
 Date:       12/07/2011 09:06 AM                                                                                                
                                                                                                                                 
 Subject:    [eclipse-dev] Planning Meeting Notes - 7 Dec 2011                                                                  
                                                                                                                                 





Planning Meeting Notes
7 December 2011

JDT UI, JDT Text
- working towards Juno M4 (test day, bug fixing, N&N)
- adopted the 'Using annotations for null checking' feature
- bug fixing
- vacation

SWT
- fixed several memory leaks in Table and Tree on GTK
- fixed ToolItem tooltip problems in 4.2 stream (GTK and Cocoa)
- TIFF Group 4 work continuing
- testing for 4.2M4
- 3.8/4.2-stream bug triage and bug investigation

Ant
- testing towards 3.8/4.2M4
- bug triage

Debug
- merged flexible viewer refactoring (
https://bugs.eclipse.org/bugs/show_bug.cgi?id=161435)
- testing towards 3.8/4.2M4
- bug fixing / triage

Releng
M4: waiting for Jetty team to produce new bundles we can consume for our
milestone
-testing new builder bundles, new compiler
-perf baselines - you can release changes to the perf_37x branch in Git
-update to new Orbit build and Jetty bundles
-bug fixing

PDE
- M4 test pass
- 3.7.2 test failures fixed (bug 365132)
- M4 test failures fixed, waiting on next I build to verify (bug 365325)
- Regression found in new plug-in creation wizard, did not setup API Tools
correctly (bug 365661)

JDT/Core
- Working towards Juno M4 (test day, bug fixing, N&N)
- Verification went OK, a few minor issues here and there, nothing major.
- Released support for null analysis via null annotations.
   See
https://bugs.eclipse.org/bugs/show_bug.cgi?id=186342
- Had the customary milestone week visitation by the git monster:
   See
https://bugs.eclipse.org/bugs/show_bug.cgi?id=365778
- No more planned items for M4 at this point.

Performances:
3.8
- We have two baseline runs now and able to distinguish the noise.
- Have filed 365849(Platform/UI),  365846(PDE/UI) and 365841(JDT/UI)

Platform Workspace:
- Bug 363048 - Moving project into its subfolder deletes it when project
name is also changed [in progress]
- Bug 356448 - Allow GitProjectSetCapability to accept SCM URIs [fixed]
- Bug 365573 - team map is broken by SDK build [plan to fix it by Friday
before next MBuild]
- inbox tracking
- nothing more planned for M4
_______________________________________________
eclipse-dev mailing list
eclipse-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe
from this list, visit
https://dev.eclipse.org/mailman/listinfo/eclipse-dev



_______________________________________________
eclipse-dev mailing list
eclipse-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/eclipse-dev



Back to the top