Hi *, several cws have been resynced to an invalid master milestone, namely OOO300 line with m23, m28, m29 for example. Those masters don't exist yet (We're at OOO300_m2 currently)
So who's at fault here? Admins who can set any arbitrary value bypassing the checks, or are the checks broken by themselves? from tinderbox' tag-list (which tinderbox gets from EIS via SOAP - checking e.g. pflin11 shows this data is matching that in EIS web-UI): xsltfilter10 : OOO300_m23 : cws_dev300_xsltfilter10 : beanshell config_office external filter odk officecfg oovbaapi rhino scp2 solenv swext wizards xalan : stax saxon hrovista2 : OOO300_m28 : cws_bea300_hrovista2 : desktop extensions fpicker sal sfx2 : dba31a : OOO300_m28 : cws_dev300_dba31a : comphelper connectivity dbaccess default_images filter forms framework offapi officecfg reportdesign sc scp2 solenv svtools svx sw testautomation vcl wizards xmloff : pflin11 : OOO300_m29 : cws_dev300_pflin11 : basic sc : How could this happen? Will this continue to happen? ciao Christian --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
