search

sweetstuff4u / zaplink

Automatically exported from code.google.com/p/zaplink
0 stars 0 forks source link

"Person responsible" for DEVC might change #88

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1. Export DEVC using ZL_EXTRACT (with anonymize)
2. Import on other system where person resposible do not exist
3. Export DEVC using ZL_EXTRACT (with anonymize) on new system

What is the expected output?
They should identical ??

What do you see instead?
Person responsible has changed

Original issue reported on code.google.com by taryck%b...@gtempaccount.com on 30 May 2010 at 2:20

GoogleCodeExporter commented 8 years ago 
It'a point of view. We might decide person responsible of ZAPLink package is a 
user 
named "ZAPLINK". This means that all developers should have a user named 
"ZAPLINK" in 
their system in order to do not detect changes within DEVC due to change in 
responsible person...

Note: This applies also to INTF.

While ending this discussion, responsible person are cleared within DEVC and 
PINF.
This is NOT a PERMANENT SOLUTION. This might change in the future.

Original comment by taryck%b...@gtempaccount.com on 30 May 2010 at 2:24

GoogleCodeExporter commented 8 years ago 
Temporary fix with changeset : http://code.google.com/p/zaplink/source/detail?
r=30e5564171d6cc66f7a697d11e1ef483cf259f98

Original comment by taryck%b...@gtempaccount.com on 30 May 2010 at 2:49

GoogleCodeExporter commented 8 years ago 
Rollback : DEVC class of ZAPLink framework will be connected to user 'ZAPLINK'

Original comment by taryck%b...@gtempaccount.com on 4 Jun 2010 at 4:27

GoogleCodeExporter commented 8 years ago 
rollback on changeset :
https://code.google.com/p/zaplink/source/detail?r=fd32d610f2e9636d07f16afebe4958
932d0b45cc

Original comment by taryck%b...@gtempaccount.com on 4 Jun 2010 at 4:42