Bug 158562 - Startup splash.bmp should be updated with 3.3 progress.
Summary: Startup splash.bmp should be updated with 3.3 progress.
Status: RESOLVED DUPLICATE of bug 153668
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.3   Edit
Hardware: All All
: P3 minor (vote)
Target Milestone: ---   Edit
Assignee: Platform-UI-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 154088
  Show dependency tree
 
Reported: 2006-09-25 10:19 EDT by Mark A. Ziesemer CLA
Modified: 2006-09-28 09:42 EDT (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Mark A. Ziesemer CLA 2006-09-25 10:19:10 EDT
Any chance of updating the splash.bmp in the org.eclipse.platform plugin along with the 3.3 progress, possibly even with each milestone?

As I download and run several versions of Eclipse, for testing issues with previous versions and the like, it'd be nice to see the proper version displayed during startup.

I think "3.2" is just incorrect, as the code is all from the 3.3 stream.  I see how "3.3" could be misleading, as it is not yet "final".  Could it possibly be listed as "3.3M2" or whatever the (last/target ?) milestone is?  Or, if per-milestone is deemed too much work, maybe just something like "3.3 beta" until release status is achieved?

This could very easily relate to bug 154088, as if created and displayed with SWT, the version # could be easily and dynamically determined, without requiring a bitmap edit.

(For the moment, I've just manually edited the current splash bitmap, copying the "3" from "3.2" to create "3.3".  Not the best method, as it slightly interferes with the background gradient, but I don't know where the layered source for the image is - if it exists.)
Comment 1 Tod Creasey CLA 2006-09-26 08:26:04 EDT

*** This bug has been marked as a duplicate of 153668 ***
Comment 2 Jeff McAffer CLA 2006-09-28 09:42:29 EDT
I suspect that Dejan is the guy to comment on this but it is unclear what component this bug belongs to...