Issue 77330 - Installer: Version number should state 3.x.y
Summary: Installer: Version number should state 3.x.y
Alias: None
Product: Installation
Classification: Application
Component: ui (show other issues)
Version: OOo 2.2.1 RC1
Hardware: PC All
: P3 Trivial with 3 votes (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
Depends on:
Reported: 2007-05-14 08:46 UTC by merschmann
Modified: 2017-05-20 10:55 UTC (History)
5 users (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---

Places for full version number (56.65 KB, image/png)
2007-05-16 12:31 UTC, merschmann
no flags Details

Note You need to log in before you can comment on or make changes to this issue.
Description merschmann 2007-05-14 08:46:33 UTC
The installer does show always 2.2, so someone could be irritated.
We shall leave the screens, but the strings should be changed.
Comment 1 Martin Hollmichel 2007-05-16 11:53:52 UTC
Comment 2 Martin Hollmichel 2007-05-16 11:57:04 UTC
what strings are you exactly talking about ?
Comment 3 merschmann 2007-05-16 12:18:13 UTC
I am talking about the title bar and the changing content in the right part of
the installer window.
I will enclose a screenshot.
Comment 4 merschmann 2007-05-16 12:31:31 UTC
Created attachment 45137 [details]
Places for full version number
Comment 5 2007-05-16 13:28:27 UTC
IS: This works as designed. The micro version 2.2.1 can only be seen in the
AboutBox. All other bitmaps and strings in a running OOo are still 2.2.
(also the name of the RPMs contains a 2.2.1)

-> MH: Back to you. This "hiding" of micro version was your idea ;-)
Comment 6 2007-05-16 13:28:56 UTC
Comment 7 Martin Hollmichel 2007-05-16 13:47:06 UTC
ideas from whomever don't count, the spec should say the truth ! :-)

in the spec only StarOffice numbering has been referenced, so please update the
specification accordingly for

But indeed, I think having 2.2 in dialog title and content is ok for 2.2.1 now.

I also would love to see a reference to whatelse tasks have to completed when
changing the product version.

Comment 8 Martin Hollmichel 2007-05-16 13:47:51 UTC
Comment 9 matthias.mueller-prove 2007-05-16 14:22:20 UTC
change summary.
target should be OOo 2.3.1

It should be clear from the installation dialogs what version will be installed. Can we please diplay the 
complete version number for minor updates?
Comment 10 matthias.mueller-prove 2007-05-16 14:24:23 UTC
add Martin to cc
Comment 11 2007-05-16 14:35:22 UTC
Well, currently we use the one variable PRODUCTVERSION. This is defined in
instsetoo_native and used for installation and for OOo. This is 2.2. We will
change it for an OOo 2.3 .Together with this variable we will change the bitmaps
for the installation. 
Especially for the AboutBox we introduced a new variable ABOUTBOXPRODUCTVERSION
that is only used for the about box. So, what changes do we want to do in future?
Do we want to change PRODUCTVERSION to 2.3.1 ? Or only selected bitmaps, that
can be changed independently from PRODUCTVERSION?

IS -> MMP: Sending to you, because you have to make more investigations.
Comment 12 matthias.mueller-prove 2007-05-16 15:04:22 UTC
sounds good. The bitmaps can remain in "OOo major.minor" format. "OOo major.minor.micro" should be 
the strings for the installer as highlighted in the attachment.
Example " 2.3.1"

PRODUCTVERSION should remain "major.minor". This saves some clutter from window titles of for instance 
alert dialog.
Example with PRODUCTNAME: " 2.3"

ABOUTBOXPRODUCTVERSION will be then "major.minor.micro" and used for the about box.
Example with PRODUCTNAME: " 2.3.1"
Comment 13 2007-05-16 16:43:09 UTC
IS -> MMP: No, you did not understand me. The installer has a variable
PRODUCTVERSION, that is used during installation. This is shown in all
installation dialogs, in the default directory name, many many Windows registry
values, ... . This variable is written during packaging process into the
configuration. Therefore this variable is also available for OOo. If we change
the variable to 2.3.1 for the installation (which is of course very easy), we
will also change the  default installation directory, many many registry entries
and last but not least the version of OOo.  Using different numbers for
Installer and OOo will be very dangerous. It would be simpler only to change
some bitmaps, but this has to be specified by user experience.
This is still one for you.
Comment 14 matthias.mueller-prove 2007-05-16 17:02:31 UTC
This is what I understood:
PRODUCTNAME and PRODUCTVERSION are variables for OOo runtime. 
ABOUTBOXPRODUCTVERSION should be a new variable for OOo runtime.

The installer uses also variables:
PRODUCTVERSION (same name, different application) is used to create paths and registry entries for 
OOo (as you just said)
Its value will then be forwarded to define PRODUCTVERSION for OOo runtime.

Then how is ABOUTBOXPRODUCTVERSION defined for OOo runtime?

Bitmaps: They are used for the installer, for the splash, and for the about box. 
They can remain "PRODUCTNAME major.minor" - without "micro"
But the highlighted areas in the attached image are strings. Where do they come from?

Can we use ABOUTBOXPRODUCTVERSION for the installer, whereever the version number is visible to 
the user, and continue to use PRODUCTVERSION where paths and registry entries are created?
Comment 15 matthias.mueller-prove 2007-05-24 12:38:42 UTC
Hi Martin,
I suggest to update the bitmaps also for minor versions with x.y.z version
In addition the displayed version string in the setup/installer should get an
".1" string added.

Is this ok for you, Martin?
Comment 16 2007-05-24 12:48:33 UTC
The displayed version string in the installer should only be changed at very
selected places. We cannot change it completely. I would have to introduce a new
variable containing the ".1" in many many strings (probably some hundred
strings, with localization many thousand strings). That is probably not what we
Changing the bitmaps is no problem, but every string is difficult and
translation relevant.
Comment 17 merschmann 2007-11-16 08:45:03 UTC
Showing up again with OOo 2.3.1 RC1, where everything is "2.3" except about-box.
No solution here?

Comment 18 merschmann 2008-04-24 09:13:18 UTC
I'm changing the target to 3.x, as it is not worth anymore for 2.4.1

Can this be managed with our repackaging for 3.x ?
Comment 19 merschmann 2008-04-24 09:14:44 UTC
Adjusting the summary according to new target
Comment 20 merschmann 2009-01-13 21:47:44 UTC
Still true for 3.0.1 which shows 3.0 as version in its installation.

CCing UX-Lead Christoph Noack as I think this a usablity thing.
Comment 21 Marcus 2017-05-20 10:55:46 UTC
Reset assigne to the default "".