Issue 52385

Summary:	1.1.5 localized build: QA and Release
Product:	QA	Reporter:	khirano
Component:	www	Assignee:	stx123
Status:	CLOSED IRREPRODUCIBLE	QA Contact:	issues@qa <issues>
Severity:	Trivial
Priority:	P3	CC:	andre.schnabel, issues, jacqueline.mcnally, pavel, sgautier.ooo
Version:	current
Target Milestone:	---
Hardware:	PC
OS:	All
URL:	http://qa.openoffice.org/localized/status-1.1.x.html
Issue Type:	TASK	Latest Confirmation in:	---
Developer Difficulty:	---

Description khirano 2005-07-24 06:36:57 UTC

When 1.1.5rc2 localized builds are QAed and the responsible Native Language
Project QA teams say "GO" to their QAed builds, those builds under
"/contrib/rc/1.1.5rc2/" will be moved to "/localized/xx/1.1.5/" (where "xx" are
language names like fr, de, ja..) and will be given a new name such as
OOo_1.1.5_XXX_install_xx.

Now can you, Hamburg RE, handle moving of QAed Community Builds to
"/localized/xx/1.1.5/"?

ftp://ftp.linux.cz/pub/localization/OpenOffice.org/devel/645/SRX645_m57/1.1.5RC2/
Here we have 1.1.5rc2 Community Builds.

So, if responsible Native Language Project QA teams do QA with these Community
Builds and say "GO" to their QAed builds, can you move them to
"/localized/xx/1.1.5/"?

Comment 1 andreschnabel 2005-07-24 08:36:32 UTC

andreschnabel->khirano:
This is, what already had been done for several localized versions. 

The process is very simple and if followed, QA'ed builds will end pn at the
mirror network in the localized directory. (see cs, nl, da builds)

If the process is not working, this in most cases QA has not been done or the
issue to transfer the files has not been filen.

So .. I'd close as WORKSFORME.

Comment 2 stx123 2005-08-18 12:21:32 UTC

As Andre described this is current best practise. And we try to make sure that
there is no overlap in the efforts to create localized builds.
We earlier published cs, da, nl versions besides de, fr, ... in the localized
section.

Comment 3 andreschnabel 2005-09-23 10:18:24 UTC

closing, as nobody objects that it is already working