To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=69210


User ja changed the following:

                What    |Old value                 |New value
================================================================================
                      CC|'ja,st'                   |'ja,mh,st'
--------------------------------------------------------------------------------




------- Additional comments from [EMAIL PROTECTED] Tue Sep  5 09:04:48 -0700 
2006 -------
The naming of the ood680_m1 developer snapshot build wasn't as wrong as
supposed. I usually name the files like this:

OOo_2.0.180_Win32Intel_install.exe
OOo_2.0.180_LinuxIntel_install.tar.gz
OOo_2.0.180_Solarisx86_install.tar.gz
OOo_2.0.180_SolarisSparc_install.tar.gz

The 180 is the minor version name and in case of the ood680_m1 it was 1
resulting in a file name like OOo_2.0.1_<Platform>_install.<ext>

As you see the OOo_2.0.1 part was correct in this case but it really was
unfortunate.


It might be a good idea to change the naming scheme for developer snapshots to
include the master branch name and the minor version.

...like

src680_m184_Win32Intel_install.exe
src680_m184_LinuxIntel_install.tar.gz
src680_m184_Solarisx86_install.tar.gz
src680_m184_SolarisSparc_install.tar.gz

Developer snapshot builds are usually built from src680 and the ood680 that MH
uploaded was an exception because the ood680 is already a release branch. Martin
decided to upload the first build as developer snapshot...

Before I change that I need to ask several people to change it within the
packaging process. Maybe there's an issue regarding the file name length...
And I would like to know if such a naming change is accepted by others. Added MH
to CC list.



---------------------------------------------------------------------
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to