OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

plcs-dex message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Ballot issues against PLCS DIS


Hi

The PLCS pilots and the DEX work is inevitably going to identify a number of issues in the PLCS EXPRESS.

When we find issues, we should record them as a formal ballot comment against the AP.

Your national bodies will have ballot forms for you to complete, but I would strongly recommend that we record the issues in

AP issue log on SourceForge as we find them. The issue log is:

stepmod/data/application_protocols/product_life_cycle_support/dvlp/issues.xml

 

I will then collect together all issues raised and submit them as UK comments.

 

This will:

1)       ensure that all issues are raised and addressed

2)       we use the existing commenting mechanism to track issues which will make our lives a lot easier when addressing the ballot comments.

 

There is of course nothing to stop anyone raising the issues as a national ballot comment either. It just means that we will have to sort out which are new comments and which are comments recorded in the issue log.

 

Most of the EXPRESS errors are going to be selects that have not been extended.

So I propose that we:

1)       should make a copy of the existing arm long form,
e.g. stepmod/data/modules/ap239_product_life_cycle_support/arm_dvl_lf.exp. Check this into Sourceforge

2)       record the issue as above

3)       review the issue , if it is an express issues, fix the express long form, arm_dvl_lf.exp,  and update it on Sourceforge adding the issue ID into the CVS description when you check it in – that way implementations can continue

4)       update the issue with a comment stating that arm_dvl_lf.exp has been updated.

5)       after the ballot closes, raise the relevant SEDS against the modules

6)       Correct the modules

7)       Regenerate the official long form:
stepmod/data/modules/ap239_product_life_cycle_support/arm_lf.exp

If we were to fix the modules as we found errors we may end up making a fix which we have to subsequently undo.

Does the above process make sense?

Unless I hear any negative comments, I will go ahead and create arm_dvl_lf.exp

 

Regards
Rob

-------------------------------------------   
Rob Bodington
Eurostep Limited
Web Page:
http://www.eurostep.com http://www.share-a-space.com
Email: Rob.Bodington@eurostep.com
Phone: +44 (0)1454 270030
Mobile: +44 (0)7796 176 401

 



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]