Zbyszek
You have to remember that Siemens are responsible for ensuring the
stability of the public facing infrastructure.
This makes it important not to introduce new modules, or upgrade
existing modules, without an extensive
testing period to make sure it works with all existing applications. The
trouble with this is that it is easier to
keep stable (or work around existing known problems) by not installing
anything new.
Regards
Ian Docherty
Zbigniew Lukasiak wrote:
Is it possible that we go to the root of that and ask Siemens about
their policy for whitelisting modules? I can understand that they
want to keep some control over this - but if we new what process they
use for that and what criteria - then perhaps we could help them in
some way? In the age of social networking we should be able to find
someone from Siemens - what do you think?
--
Zbyszek
On Dec 2, 2007 12:06 AM, Ian Docherty <[EMAIL PROTECTED]> wrote:
I have some first-hand knowledge that could throw some light on this.
I was aware that Catalyst was being used within the iPlayer team, and they
were contributing many bug fixes back into Catalyst and DBIC. I was not
aware of this 'Perl on Rails' work. There again the BBC is big so it is not
surprising that one team does not always know what another team is doing.
Catalyst is being used only for back end systems, not customer facing. The
BBC works almost exclusively on systems that publish HTML rather than
providing dynamic content.
J. Shirley wrote:
On Dec 1, 2007 11:29 AM, Jonathan Rockway <[EMAIL PROTECTED]> wrote:
_______________________________________________
List: Catalyst@lists.scsys.co.uk
Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst
Searchable archive: http://www.mail-archive.com/[EMAIL PROTECTED]/
Dev site: http://dev.catalyst.perl.org/
