Add RUX final design acceptance milestone

[vic-georgiev]

For RUX final design selection we have to allow selection of 8 final designs, so I'll add the design based on the regular 3 winner selection.

Aha! Link: https://topcoder.aha.io/features/TCCONNECT-414

[vikasrohit]

@vic-topcoder IMO, we should consider this for next release as we might some changes in code to support the dynamic count for final design selection if we do properly, or we have to make redundant component of final designs to support 8 winner selection.

[vikasrohit]

I have moved it to the 2.4.5 milestone, please feel free to move it back if it is really urgent to get done in this release.

[vikasrohit]

@vic-topcoder Do we have the designs ready?

[maxceem]

@vikasrohit will be there some specific designs? Some description of how it suppose to work also ould help if we already have elements for milestone implemented.

[vikasrohit]

Essentially, we need to update our final-designs milestone to support a configurable number of final design selection which is right now hard code to 5. I think we need to update the milestone templates to support metadata to support this type of configuration because we don't have any field right now to store this configuration per milestone template.

[maxceem]

Do you think adding some property for such configuration in details would work?

So far we have:

details: {
   content: {},
   prevMilestoneContent: {},
   prevMilestoneType: '',
}

So we can add something like details.meta or details.config.

[vikasrohit]

I don't think that would work because for each product we have a list of milestone templates where we have to put that information so that when actual milestones are instantiated from those milestone templates, they have the correct behaviour in place.

[maxceem]

Yeah, I've missed that milestoneTemplates don't have details property. So if I get it right, first some new property has to be added to both milestoneTemplates and milestones.

[vikasrohit]

Yes, we need to add details or metadata to milestoneTemplates but no need of a new field in milestones we can copy that metadata info to the details field of the milestones, as you suggested.

We would use the metadata field on milestoneTemplates for storing roles specific messages for milestones.