This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
according to Trung decision, there will be the one ml build/installer for the 3 sun supported languages and that is being done/tracked by another issue. He mentioned that for community builds, the criteria will need to be decided as to how to release them but as for now, the way it will be done was as for nb5.5.1 which was one build for all community languages. Thus this task is to implement the infrastructure for it, but not to start any actual builds at this time. IDEA - instead of needing to add some additional language/locale to the build at different times, how about setting it up so that it will build for all langs/locales that were done or in progress for nb551 ? even if no putbacks to translated files of them yet, at least the setup will be done. and its expected that these builds will be partial translations of different languages at different times anyway; and these are the builds that community gets to verify their own work; these are not posted as is to the download pages for nb product until much later.
the schedule of community builds will be from time to time, as before; so can we setup, as mentioned below, the build to be setup for all community locales that were translated in nb55 and I'll find out some others that might be and add to this issue. ken.frank@sun.com
locales for 55 and 551 were: az cs de el es fr in it nl sq sv zh_TW these can be used as baseline for nb6 commu builds; will add others later when know plans.
lets add these locales also, based on translation team comments: pt_PT ko ru
translation team wonders if this setup can be done before the 11/15 date I had put on nb schedule ? I had assumed that community work would happen after sun supported ml builds (ja,zh, pt_BR) but for nb6 the community is starting their work earlier. Thanks - Ken
Yes, we should be able to make setup for community builds before 11/15.
I see that questions Trung asked to translation team have been answered and we can see what he says as to direction for community builds. I am guessing that since ml builds for ja/zh/pt_BR already setup that it will be easier to do it for community ones,esp if can setup all known possible locales that will be translated, the first time, as mentioned other places in this issue. I'll update issue when see reply from Trung. ken.frank@sun.com
can the community builds be setup as suggested so that it will cover all expected community locales, so not to need separate requests and process for each new community locale ? ken.frank@sun.com
I'm in the process of setting up a build at http://deadlock.netbeans.org/hudson/job/nb6-community-ml/
The NB 6 community ML build has been setup. It's NBM-only build. Get the latest successful build results at http://deadlock.netbeans.org/hudson/job/nb6-community-ml/lastSuccessfulBuild/artifact/nbbuild/dist/nbms/ . It's now configured to run for locales from following list "az cs de el es fr in it nl sq sv zh_TW pt_PT ko ru". This list is hardcoded as part of build job script. If you want to change this list, you have to contact NetBeans Build Engineering to change it. We can also find other how to put it under someone else's control (i.e. in a property file under translatedfiles module). * The build produces Update Center catalogs for each locale and one catalog for all locales * Result NBMs do have specification version number based on date and time mask "YYYY.MM.DD.HHmm". This causes that each build shows up as an update in your IDE (no matter if there really was or was not a change). * Initial schedule is to run a build Monday to Friday at 9am CET (UTC +01:00). Feel free to propose different schedule. * Suggested Update Center catalog URL is http://deadlock.netbeans.org/hudson/job/nb6-community-ml/lastSuccessfulBuild/artifact/nbbuild/dist/nbms/catalog_${locale}.xml Where locale could be either "all" or from the list mentioned above. * This localization comes for ALL clusters independently on fact which clusters user really installed. If you will install some cluster later, the localization will work out of the box. * These localization NBMs are one NBM per functional cluster (platform7,ide8 etc.) They introduce new codenames just for localization. * Current implementation auto-generates text displayed in Update Client, which is actually always English. Feel free to file RFE to localize/change these strings.
Rudolf, Thanks for setting this up and in covering all the various locales that translation people felt would be in progress in near term ! I think/hope it will save BE time in not needing to get many mails and requests to add one by one such additional locales. Is the next step, for getting actual installers, for me to contact installer team and point them to these builds, so they can then do whatever is needed so installers of the community build can be created ? Thanks - Ken ken.frank@sun.com
as per 124082, it seems in sun supported ml build, that most of the modules in visualweb1/modules/ext/locale are not being built. Thus perhaps some additional setup is needed so the community nbms of those will be built ? ken.frank@sun.com
please reply to last question below - are other steps or other issue should be filed for needing to get actual installers of the community builds ? ken.frank@sun.com