John,
I am not sure this is such a great idea. First,
Callisto and Europa are names that were created to reference a specific event,
the release of multiple Eclipse projects. It was not intended to
identify a particular thing, project or technology. Second, I don’t
think we want people to start calling the SDK, Europa or Callisto, since
this will start to weaken the Eclipse name. In fact, we are
actively trying to stop using the Callisto name, so if the SDK started having
this in the splash screen it would be counter to this approach.
My preference is that you stick with
version numbers to identify the SDK releases.
Ian
From: eclipse-dev-bounces@xxxxxxxxxxx
[mailto:eclipse-dev-bounces@xxxxxxxxxxx] On
Behalf Of John Arthorne
Sent: November 8, 2006 12:04 PM
To: General development mailing
list of the Eclipse project.
Subject: Re: [eclipse-dev]
Planning Meeting Notes - Nov 8, 2006
For those interested, the outcome of the discussion
topic below is that we generally agree that adopting the Eclipse Foundation release
naming is a good idea. I..e, begin referring to the next release of the Eclipse
SDK as "Europa" rather than "3.3". This has absolutely no
impact on the mechanics and version numbers of plugins and features. The most
obvious place this will likely show up is in the Eclipse splash screen. This
actually brings us more in line with the rest of the world, who have
consistently referred to the previous release as "Callisto" while we
kept calling it "3.2". Discussion and comments from the community
appreciated...
(And
yes, we already know this will confuse some Austrians...
https://bugs.eclipse.org/bugs/show_bug.cgi?id=147754#c10)
John
|
Mike Wilson/Ottawa/IBM@IBMCA
Sent
by: eclipse-dev-bounces@xxxxxxxxxxx
08/11/2006 08:57 AM
|
Please
respond to
"General development mailing list of the Eclipse project."
<eclipse-dev@xxxxxxxxxxx>
|
|
|
To
|
eclipse-dev@xxxxxxxxxxx
|
|
cc
|
|
|
Subject
|
[eclipse-dev] Planning Meeting Notes - Nov 8,
2006
|
|
------------
Discussion
------------
Workspace:
- Plugin version numbers no longer match the
version we attach to the
release overall: Eclipse 3.2.2, Eclipse
3.3., etc. Should we re-brand
our releases to avoid using these numbers?
I.e., change our plans,
documentation, splash screen, etc, to refer
to "Eclipse Callisto Fall
Update" or "Eclipse Europa"
rather than numbers? This would harmonize
with other Eclipse projects, and prevent the
desire to "cheat" and align
our feature and plugin versions with a
release number that has lost its
original meaning.
----------
Outreach
----------
**** Happy Birthday, Eclipse! ****
Platform/JDT Text:
- interview together with the Zurich team for the
Eclipse Magazine:
- http://www.eclipsemag.net
--------
Status
--------
Platform UI:
- XSLT:
- OSGi transformation
- M3 testing/verifying
- saving settings:
- configuration level settings
- sharing settings within a working set
- Windows Vista:
- testing
- commands:
- gathered feedback on menu API
- learning about menus
- investigating dynamic menus
- quick access:
- persisting selections
- search dialogs:
- bug fixing and refactoring in Resource dialogs
- preparing patch for JDT (Type dialogs)
- status handling & error dialog story:
- implementation
- preparing long talk abstract about Status
Handling for EclipseCon
- viewers:
- looking at Debug's async tree viewer
framework
- data binding:
- progress on observable map and tree
JDT UI:
- 3.3M3 testing and shipping
- preparing 5 year Eclipse anniversary
presentation
- bugfixing:
- improved presentation and filtering of
derived resources in refactoring
preview
- stale entries / wrong labels in open type
dialog
- copy in call hierarchy
Platform/JDT Text:
- shipped 3.3 M3
- 3.3 M4 planning
- compiled wish list for JDT Core
- preparations for 5th Eclipse anniversary party
- inbox tracking
Runtime:
- contributed pde console view to pde/ui
- getting Orbit up and running
- added new bundles to Orbit from equinox-incubator
- preference work related to shared settings
- releasing lazy-start code
- splash screen work - prototype done for windows
using JNI
- work on API tooling
- make Wassim's day by adding JAR signing to the
builds
- Eclipse 3.3 M3 work
- bug triage and fixing
Debug:
- M3 test pass
- bug fixing
- M4 planning
PDE:
- filtered tree added to the plug-in registry view
- work continues on Ctrl+O support for the source
pages of the
manifest editor
- considering tooling support for breaking plug-ns
into smaller plug-ins
- 'Save As' implemented for both simple and
composite cheat sheet editors
- cheat sheet creation workflow:
- adding support for automatically creating
cheat sheet extension from
the cheat sheet editor
- lots of bug fixes
- brian is on honeymoon
User Assistance:
- work continues on dynamic content support across
the UA
- help model fully supports it, working on
cheat sheets now
- work continues on the Ajax-based TOC tree view
in the help web application _______________________________________________
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
