[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [eclipse-dev] Post Planning Meeting Notes - Apr 8, 2009

A question regarding http://wiki.eclipse.org/Polish3.5

I'm not sure what is the rule to put items on the list. I understand that
there are some issues people would like to have fixed,
however it doesn't make sense to put them on the list if the team
responsible for fixing the issues is not going to handle it.

So if there are items not planned for 3.5, target milestone is not set and
one put this issue to the list, how should I understand it?
If these items are really important, it should be at least discussed with
component leads or developers responsible for such issues.

Thanks
--
Szymon Brandys



                                                                           
             Boris Bokowski                                                
             <Boris_Bokowski@c                                             
             a.ibm.com>                                                 To 
             Sent by:                  eclipse-dev@xxxxxxxxxxx             
             eclipse-dev-bounc                                          cc 
             es@xxxxxxxxxxx                                                
                                                                   Subject 
                                       [eclipse-dev] Post Planning Meeting 
             2009-04-08 19:52          Notes - Apr 8, 2009                 
                                                                           
                                                                           
             Please respond to                                             
                 "General                                                  
                development                                                
              mailing list of                                              
                the Eclipse                                                
                 project."                                                 
             <eclipse-dev@ecli                                             
                 pse.org>                                                  
                                                                           
                                                                           




Performance action item for next week:
            Every performance bug needs to be looked at. Understand what's
            going on and at least comment on the bug if you cannot resolve
            it. The top-level bug for this is
            https://bugs.eclipse.org/bugs/show_bug.cgi?id=270824


"Be a good citizen" action items:
            Babel NLS key freeze is M7. To check map files submitted to
            Babel, use: http://babel.eclipse.org/babel/importing.php.
            (after login, use "eclipse", "3.5", "galileo" to see the
            current map files)
            Now is a good time to check version bounds. The easiest
            approach is to set lower bounds to the latest if you are not
            testing against older versions.
            For the 3.5 polish pass, use http://wiki.eclipse.org/Polish3.5
            (to add new entries, copy an existing one to ensure
            consistency, and don't forget your name).

FYI items:
            The Eclipse SDK plan document has wrong dates for the RC
            milestones. A plan update is coming this week to match release
            train dates.
            How to attach YourKit to performance tests running in the test
            framework:
            http://wiki.eclipse.org/Automated_Testing#Profiling_performance_tests

Boris_______________________________________________
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