Am 11/09/2012 10:30 PM, schrieb jan iversen:
Hi.
In order to make life easier (more stable) for translators, I think it
would be a good idea to "isolate" developer builds on dev. When we have
langauge packs integrated, then we could point to them from l10n, with a
thick note, stating they are only there for testing the language.
I don't know what you mean with this. But I thought of a page like the
download/other.html.
It's to get more attention to dev builds. And a little extra "promotion"
in the kind of a separate download webpage (that is seen by more people
than the Wiki page) would give more chances for feedback.
However, this is just my opinion and I can live with it if there is no
majority.
In order to make sure they dont get distributed "as released", would it be
an idea (and is it possible) to e.g. disable the actual "save" (not the
button, but the final write call). With such a feature anybody can test
(which is the purpose) but it cannot be used as a product.
Dev builds are different products. So, it don't get installed as
OpenOffice but as OOo-Dev. This is valid also for the names or
directories and therefore user profiles. No interference with the
production installation.
Marcus
On 9 November 2012 22:05, Rob Weir<robw...@apache.org> wrote:
On Fri, Nov 9, 2012 at 3:55 PM, Marcus (OOo)<marcus.m...@wtnet.de> wrote:
Hi all,
a quick question as I don't know the status of this request:
Do we (still) want to have download links for Dev Builds that refer to
the
respective people's dir?
IMHO we don't want pages in www.openoffice.org/dowload/* to point to
anything other than actual releases. Links from Dev, L10n or QA
pages are fine.
Then I would create a webpage that can be included in the usual download
website - as it was in the former times with OOo.
At the moment there is just a link to the Wiki page.
Marcus
