("The temporal stance indicator light is now properly scaled and positioned for the TOS Temporal Light Cruiser, T’Liss, and D7"). that is fixed on LIVE server is WRONG AGAIN on Tribble as of 21 Sep 2016 build
("The temporal stance indicator light is now properly scaled and positioned for the TOS Temporal Light Cruiser, T’Liss, and D7"). that is fixed on LIVE server is WRONG AGAIN on Tribble as of 21 Sep 2016 build
The fix on Holodeck server has not been added to the branch that tribble server is on right now because the current tribble patch was created long before the fixed was added to redshirt and holodeck and will most likely is already added in the next patch.
With tribble being used for 3.5 expansion update any fix or change for holodeck creates twice the work for the Devs.
("The temporal stance indicator light is now properly scaled and positioned for the TOS Temporal Light Cruiser, T’Liss, and D7"). that is fixed on LIVE server is WRONG AGAIN on Tribble as of 21 Sep 2016 build
The fix on Holodeck server has not been added to the branch that tribble server is on right now because the current tribble patch was created long before the fixed was added to redshirt and holodeck and will most likely is already added in the next patch.
With tribble being used for 3.5 expansion update any fix or change for holodeck creates twice the work for the Devs.
The following statements only apply when Redshirt is being used for weekly updates and Tribble is being used for long-ter testing.
If nobody has touched the files in the Tribble data branch that Thomas changed in the live data branch to fix that issue, the ideal case, then he does not need to touch them again on the Tribble branch to fix them. However, we do still need to do a push that includes that fix, which we have not done. It does create twice the work for QA, who does have to verify the fix on both builds.
Due to the need for those fixes on Holodeck vs Tribble; things that we take quickly for Holodeck (such as fixes to recently released things) are likely to be delayed for Tribble, and the opposite also applies.
If we took it quickly to Redshirt and then Holodeck, there is no need to rush it to Tribble, and we do the opposite as a general rule. This decreases the number of changes that are made to what's on Tribble in most patches, which minimzes the QA work needed for each patch and decreases the number of changes that need to be looked at if something broke.
Fixes to live issues that you see on Tribble and not immediately on Redshirt are likely to be delayed going to Holodeck. This may happen because the fix requires a code change, which are generally taken live at a slower pace, because the fix is not a priority (such as an extra space in an item's name), or because the fix was made in the Tribble branch and not the Holodeck one, as some examples.
The D7/TOS Connie/T'Liss lights will be fixed on Tribble soon; there is nothing to be alarmed about in that case.
Here are things that would be a significant cause for concern if they were fine on Holodeck and not on Tribble (The examples I am using are ones that currently are happening):
Things being broken that were not recently (within the past month) patched on Holodeck. (such as the ShowFPS command)
Abilities or Traits being missing. (Such as an inability to use lockbox training manuals)
Skills being invalid.
Items being deleted (Such as kits)
Anything related to a new feature that is currently on Tribble (Such as the lighting changes)
Comments
The fix on Holodeck server has not been added to the branch that tribble server is on right now because the current tribble patch was created long before the fixed was added to redshirt and holodeck and will most likely is already added in the next patch.
With tribble being used for 3.5 expansion update any fix or change for holodeck creates twice the work for the Devs.
The following statements only apply when Redshirt is being used for weekly updates and Tribble is being used for long-ter testing.
If nobody has touched the files in the Tribble data branch that Thomas changed in the live data branch to fix that issue, the ideal case, then he does not need to touch them again on the Tribble branch to fix them. However, we do still need to do a push that includes that fix, which we have not done. It does create twice the work for QA, who does have to verify the fix on both builds.
Due to the need for those fixes on Holodeck vs Tribble; things that we take quickly for Holodeck (such as fixes to recently released things) are likely to be delayed for Tribble, and the opposite also applies.
If we took it quickly to Redshirt and then Holodeck, there is no need to rush it to Tribble, and we do the opposite as a general rule. This decreases the number of changes that are made to what's on Tribble in most patches, which minimzes the QA work needed for each patch and decreases the number of changes that need to be looked at if something broke.
Fixes to live issues that you see on Tribble and not immediately on Redshirt are likely to be delayed going to Holodeck. This may happen because the fix requires a code change, which are generally taken live at a slower pace, because the fix is not a priority (such as an extra space in an item's name), or because the fix was made in the Tribble branch and not the Holodeck one, as some examples.
The D7/TOS Connie/T'Liss lights will be fixed on Tribble soon; there is nothing to be alarmed about in that case.
Here are things that would be a significant cause for concern if they were fine on Holodeck and not on Tribble (The examples I am using are ones that currently are happening):
Hopefully this clarifies some things.