Voters should see blue star on trunk item

Description

From design doc: https://docs.google.com/document/d/1XLory27UK6Dh7LJZjR_8NbkjAuDbHHsiNjY2rpjAiRs/edit#heading=h.9anhwsqjjg0l

(better formatting is in link)
Desired behavior (different than current) [need consensus|Mark,...]:
blue-star should be master (trunk = last release plus the latest XML fixes)
Previous release is done and released (i.e. the publication of the release is done).
in XML, locale/path1=x
2 weeks later, after bug fix, still before submission/shakedown starts (ST not open)
XML changed so locale/path1=y
Shakedown/Submission starts
Voters should see blue star on locale/path1=y
y will be the winning vote, since there aren't votes to change
2 weeks later, after bug fix2 (during either Submission or Vetting, nobody has voted)
XML changed so locale/path1=z
Verify that the checkin to SVN and push to server updates the production ST to have locale/path1=z
Voters should see blue star on locale/path1=z (Verify after 3a is fixed)
z will be the winning vote, since there aren't votes to change
ST exported to VXML
locale/path1=z
(Tom: I think this conflates last-release = star with trunk = svn; ST does use trunk to determine winning sometimes, but that’s not obvious in the interface, bug-fix svn change seems to come out of nowhere)

Work item breakdown
1. Address “Voters should see blue star on locale/path1=y” at start of Shakedown/Submission.
2. Verify that the checkin to SVN and push to server updates the production ST to have locale/path=z
3. Verify Voters should see blue star on locale/path1=z
4. Translation guide update to explain Blue start as last release plus latest XML fixes by TCs.

xpath

None

locale

None

Status

Priority

critical

Assignee

Thomas Bishop

Reporter

Kristi Lee

tracReporter

kristi

Reviewer

Mark Davis

Labels

Components

Fix versions

phase

dsub
Configure