This is in relation to
      
      
      
        It appears that a back port from Photon to the
          Papyrus 3.0 maintenance stream has dependencies on Photon
          (4.0) bundles… and the use of a unit test component has
          results in problems for Papyrus-RT (go read bug
 531432 for more information).
 
      
      
      The result is that it is no longer possible to
        build Papyrus-RT, which means that we cannot provide fixes. This
        has the side effect (reported by one user thus far) that it is
        no longer possible to install the Papyrus-RT development
        environment by following the instructions in the wiki. This
        means that currently, Papyrus-RT cannot be used as a base for
        further customization, as indicated by an affected external user
        (who may not be a user for long…).
      
      
      
        This is an example of a “very bad thing” that
          could easily be called a lack of “industrialness” in Papyrus
          and our approach. I am hopeful that it is not worse and not a
          manifestation of  siloed thinking by our teams.
       
      
      
      I do understand that, this particular problem has
        been going on for some time and that it has been discussed
        already. This should make finding a solution.
      
      
      We now have a risk identified, let's work at
        establishing governance for this risk and implement compliance
        checks.
      
      
      This needs to be addressed in the context of the
        joint PMC-Arch efforts on delivery governance and quality.
      
      
      We were lucky in that this does not seem to have
        affected many users. We may not be as lucky next time…
      
      
      If the Papyrus IC (and Papyrus product line) wants
        to be taken seriously, it can never happen again!
      
      
      I would like to invite anyone interested in
        the Papyrus IC product line Delivery Governance, including the Quality Framework &
          Testing to contact either the Architecture Committee lead (Rémi
          Schnekenburger) or myself (for the Product Management
          Committee).
      
      
      
      
      
        
          
            Regards / cordialement,
              
              Charles Rivet
              Senior Product Manager / directeur principal de produits
              - Zeligsoft
              Chairman, Papyrus IC Product Management Committee /
              président du comité de gestion de produits du consortium
              industriel de Papyrus
              
charles@xxxxxxxxxxxxx
            
            
           
         
        
        
       
      
      
      
      
      _______________________________________________
papyrus-ic mailing list
papyrus-ic@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/papyrus-ic