-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Iterate through ReleaseBranch objects before submitting build requests #323
Comments
As we continued to discuss this, we recognized that there isn't any value in requesting rebuilds of the
We will need to take this into account when implementing this. Let's make sure that we don't request builds for the |
@liammulh - I'm going to unassign myself from this issue, since it doesn't seem worthwhile to implement this in Rosetta 1 with Rosetta 2.0 so close. Please double check it's implemented and has been tested in Rosetta 2.0. |
We did not plan to add this to Rosetta 2.0, and it isn't implemented in Rosetta 2.0. I believe the plan was to add the patch to 1.0, and once that was done, it would be added to 2.0. I am happy to add the patch, but since Rosetta 2.0 is already in testing, I don't think it makes sense to add this and then do another yet another spot check before deploying 2.0. |
@jbphet and I talked about this on Friday, and we recall this was an extra thing to do on top of the work we did to add PhET-iO build request support, but we need more context on this from @jonathanolson before we implement this. |
This was discussed in a meeting on 6/14/2023 and @kathy-phet says that this is high priority and, once it is working, we should push out anything that was NOT published as a result of the lack of this feature. |
The sims that currently could have out-of-date translations are the ones that have previously released phet-io versions that are still active and that are not the main branch, and where the previous branch is not one with a
Once I've added the code to Rosetta to request builds for all active phet-io branches, I'll need to go through this list and see if any of them need to have their translations updated. I will probably create some sort of script to help in this effort. |
The code to submit requests for previous phet-io releases has been added, and as of this writing I've tested it locally and on ox-dev. I can't fully test it on the main server because it would affect real translations (this is where the capability described in #113 would be extremely helpful), so I've deployed it there and set a calendar reminder to check for submissions by real translators for one of the sims listed above. |
For reference, these change were deployed to the live version of Rosetta on Sep 08 15:32:10, so I'll need to check submissions after that timestamp to verify that things are working correctly. |
I verified that there are translations successfully being submitted and deployed after these changes were made, which is a good regression test. However, as of this moment there have been no deployments of the sims listed above, so I've not yet verified the changes for deploying translations for previous phet-io releases. |
There was a maintenance action on August 24th that republished many of the phet-io sims, and I verified with @jonathanolson that such actions rebuild the |
I think this is done, but I am going to leave it open until we get at least one translation submitted for a sim that has a supported older phet-io branch. That might take a while, so I have a weekly reminder on my calendar. I'm going to reduce the priority in the mean time. |
I just checked Rosetta's log and found that a I was also able to see evidence of there being multiple build requests, one for each of these versions, submitted to the build server. Here is an excerpt from the log that shows this:
I think I can safely close this issue now. |
In our conversation with @kathy-phet and @jonathanolson about #322, we realized that we aren't sending build requests for active phet-io branches that don't match the current current published phet brand branch. To fix this, @jonathanolson suggested we use the ReleaseBranch.js module in phetsims/perennial to identify all active phet and phet-io branches that we need to request builds for.
What this will look like is using the ReleaseBranch.js module to get a list of ReleaseBranch objects. We will then iterate over those objects, and create build request objects for each object where isReleased is true. We decided that we should include the branch that we get from the ReleaseBranch objects in the build request objects.
Here is some sample code that @jonathanolson created:
Be careful to pass false as the second parameter to the getMaintenanceBranches method so that it will obtain the information needed only from the sim metadata, rather than from a parallel checkout of the sim repos.
Here is the location of the code we need in perennial: https://github.com/phetsims/perennial/blob/6606be0cdcc1dc7b6bd6eb25b6f1bf7b7343322f/js/common/ReleaseBranch.js#L659-L661.
The text was updated successfully, but these errors were encountered: