owner:esanchez@yaco.es resolution_fixed type_task | by esanchez@yaco.es
Change the liaisons models and migrate the data to the new models. Here are some guidelines:
Events will have to be synthesized from the current submitted, modified, and approved fields.
Legacy statements will have 0 or 1 RelatedLiaisonStatement object, depending on the current related_to field.
The reply_to and response_contact fields from the current model will be combined into the response_contacts field in the new model. The migration will add a comment event capturing the original field contents.
The data migration will ensure that to_groups and from_groups always reference at least one Group. In the current data, 484 statements have an empty to_group, and 245 statements have an empty from_group. For those statements, the UI currently displays the to and from groups using the from_name and to_name fields. The migration will determine the appropriate Group objects to point to based those fields, which will require some manual inspection. Typical typical from_name and to_name entries look like “SIP”, “The IETF”, or “The IESG and the IAB”. More complicated entries look like “SG17, SG13, SG11, JCA-NID, ETSI TISPAN WG4, 3GPP TSG CT4, IESG”. After migration, from_name and to_name are expected to primarily be empty, only having content for exceptional cases. The ‘name’ function in the LiaisonStatement class will be changed to return the contents of to_name and from_name when they are not empty.
Issue migrated from trac:1424 at 2022-03-04 03:46:00 +0000
owner:esanchez@yaco.esresolution_fixedtype_task| by esanchez@yaco.esChange the liaisons models and migrate the data to the new models. Here are some guidelines:
Events will have to be synthesized from the current submitted, modified, and approved fields.
Legacy statements will have 0 or 1 RelatedLiaisonStatement object, depending on the current related_to field.
The reply_to and response_contact fields from the current model will be combined into the response_contacts field in the new model. The migration will add a comment event capturing the original field contents.
The data migration will ensure that to_groups and from_groups always reference at least one Group. In the current data, 484 statements have an empty to_group, and 245 statements have an empty from_group. For those statements, the UI currently displays the to and from groups using the from_name and to_name fields. The migration will determine the appropriate Group objects to point to based those fields, which will require some manual inspection. Typical typical from_name and to_name entries look like “SIP”, “The IETF”, or “The IESG and the IAB”. More complicated entries look like “SG17, SG13, SG11, JCA-NID, ETSI TISPAN WG4, 3GPP TSG CT4, IESG”. After migration, from_name and to_name are expected to primarily be empty, only having content for exceptional cases. The ‘name’ function in the LiaisonStatement class will be changed to return the contents of to_name and from_name when they are not empty.
Issue migrated from trac:1424 at 2022-03-04 03:46:00 +0000