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.
Summary: | I18N - L10N blocker related to clearcase module - not in l10n kit | ||
---|---|---|---|
Product: | updatecenters | Reporter: | Ken Frank <kfrank> |
Component: | Stable | Assignee: | Autoupdate Masters <aumasters> |
Status: | RESOLVED WONTFIX | ||
Severity: | blocker | CC: | msandor, ppis, rbalada, tstupka |
Priority: | P2 | ||
Version: | 6.x | ||
Hardware: | Sun | ||
OS: | All | ||
Issue Type: | DEFECT | Exception Reporter: |
Description
Ken Frank
2008-05-15 17:09:58 UTC
Peter, can you add netbeans user name of developer who needs to see this issue to cc list ? Thanks - Ken ken.frank@sun.com Peter, is the i18n support tested in ClearCase plugin? Thanks! Yes, i18n was done, and everything should be ok. Michale, can you please include the ClearCase plugin in l10n kit generation? Thanks! I can't add it to any L10N kit for 6.1 it is not included in any 6.1 production build. If any module should be on stable UC then it has to be in release61 (main) repository and in stableuc module config. But shouldn't this stay open and be assigned back to providing team to do what is needed so that it can be in kit (ie get it into production build) ? I'll reopen it for now. Does it mean other stable uc modules (most of which not in product) are in production builds ? If so, it seems that clearcase team would need to do what is needed to get it into production build ? ken.frank@sun.com to clearcase developers, please reply: if its meant to be translated ? if so, based on Michal's comments, seems it would need to be setup like other modules in production build, so can be in kit, and also would need this so it can be built for translation team testing - can this be done ? other question - is it going to be in 6.5 product or still stable uc ? ken.frank@sun.com I do not know if it is meant to be translated for 6.1 - who decides? We can just leave it as is for 6.1, I would recommend that if you don't mind. For 6.5 it will be in the main repository (for 6.1 it is in contrib) and published on stable AUC so I would recommend a standard process for stable AUC modules. I agree with Maros comments that its best to wait until its in main repos for 6.5 so can easily be part of uc l10n kit then. I will update uc web page about this. And since 6.5 is relatively short release, and cc module will have even more features for 6.5 timeframe it means translation of it won't be that much delayed. if you agree, can you close this issue ? as to who decides if should be translated - that is decided by providing team, thus your team. that is, some modules to uc are non nb api docs or samples only, which are not translated. this one is usual kind of module which IMO would be translated. BTW, for when its in 6.5 repos, please communicate to BE that it is to be in uc kit, not product kit. ken.frank@sun.com I think we can close this issue then and I will notify BE about cc being on stable 6.5 AUC. closing as per discussion in this issue. ken.frank@sun.com |