Rimas Kudelis wrote:
Hi Rimas,
thanks for your work! :) I have a few notes though. Or basically, maybe
it's just one note.
How visible will those builds be? I think we've agreed that they should
I haven't seen the agreement. In which mail was it?
be visible, and I'm not so sure hiding them behind Download -> Get More
Platforms and Languages -> Developer Snapshots -> Fourth Link makes
them visible.
this will be the start, yes. But I don't think we need several link
level. I can put it directly on "http://download.openoffice.org"; and
"http://download.openoffice.org/next";.
I would propose to merge the two pages you created with main
http://download.openoffice.org/other.html and
http://download.openoffice.org/langpack.html respectively.
I've tried this but don't liked it because IMHO this is too much content
for a single page.
Untested builds could be listed in the same table as tested builds, or
in a new one. In case of former, the resulting download table could look
something like this:
OK, with the hint of "Untested" it could work. I've to play with this setup.
All "Untested" items here should of course be linked. Expanding the
table like that would obviously make it taller. In order not to clutter
it, there could be a checkbox/button on the page which (un)hides
untested builds.
Thinking further, I think language pack downloads could also be
integrated into the same page in a similar fashion (they could be listed
in a separate hideable table, or in the same one). This should help the
users save a few clicks, or at least a few redirects.
Yes.
So, just to be sure. Do you agree to make the all install and all
langpack builds available in 2 seaparate websites? You don't want to
have every build and file on one website, right?
At least me not as it would be a monster of table. ;-)
Best regards
Marcus
2009.11.02 13:07, Marcus Lange ras(e.:
Hi all,
as promised I thought about a new structure and have created the
following websites to ease the download of RC builds:
http://download.openoffice.org/next/other_rc.html
http://download.openoffice.org/next/langpack_rc.html
Please have a look if the names of the languages are correct. It's not
easy to find the correct wording for so many, so please bear with me. ;-)
Keep in mind that this is just a test to show you how it could look
like. It's not yet the final version (e.g., all builds that are
already released have to be deleted from here, of course).
Once we have a final state I would update the index page
(http://download.openoffice.org/next), so that both new websites can
be found via links and make some announcements.
Please tell me what you think about this.
Thanks in advance.
Best regards
Marcus
Marcus Lange wrote:
Hi all,
I think I haven't taken into account the many differences with
builds, testing and NL communities. So, I'm sorry if anyone feels
offend. This was not my intension or to ignore the situation.
I'll think about what could be done to provide the builds to the
users (tested or not, released or not). Because it's a very high
number this will be not easy. And take into account that someone has
to maintain this monster of list (7 platforms with 90+ languages). ;-)
Just wanted to take the chance to answer here early before my absence
the next week. Therefore please don't expect to have a fast solution.
Best regards
Marcus
Ankit Patel wrote:
+1 to the discussion.
Having a download page for all localized OpenOffice.org language
packs where two different categories, one for "supported & tested"
versions of language packs and another for "beta & untested though
translated" versions of language packs, listed would solve the
matter I believe.
--- On Sat, 17/10/09, Mechtilde <o...@mechtilde.de> wrote:
From: Mechtilde <o...@mechtilde.de>
Subject: Re: [l10n-dev] New home for downloading language packs
To: dev@l10n.openoffice.org
Date: Saturday, 17 October, 2009, 1:44 PM
Hello,
Martin Srebotnjak schrieb:
Hi all,
Also, just out of my curiosity, can you list recent
examples when a
fully localized national sdf with gsicheck passed
successfully (no
errors nor warnings) did not work as expected (like
crashed etc.)?
Yes, we have
E.g. the Polish Win version didn't start after installing.
The goal of the NL version tests should be that it is
usable for the
normal user and didn't have severe bugs which are not in
the EN version.
It is not the goal that the NL version has to be better
than the EN version.
Finally - as these tests are already automatic in many
ways - could
not this process be automatized even further, so that
with any RC
build the tests would be made automatically by OOo
servers for all
available languages and the teams should only go
through visual
(screenshots) and text results neatly organized and
published on the
website (like a 3-5 minute job) and vote either YES or
NO at the end?
The only prerequisite for teams would be to fully
localize the tests
(another po file in the tree and in Pootle) used by
this system.
The automatic tests cannot provide you for such things like
described
above. But they can easy detect by some manual tests
Regards
Mechtilde
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org
For additional commands, e-mail: dev-h...@l10n.openoffice.org
