-
Notifications
You must be signed in to change notification settings - Fork 7
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
Natural Selection 1.3 release (4/30/2021) #251
Comments
In 10/1/2020 status meeting, @kathy-phet and @ariel-phet said:
|
Self-assigning. @ariel-phet asked me to proceed with 1.3 release, and get an RC into the QA pipeline. |
@ariel-phet You asked me to get an RC into the QA pipeline. But I just noticed that our plan in #251 (comment) is to do a full dev test before RC testing. Do you want to follow that plan and start with a dev test, or modify that plan and go immediately to RC testing? |
@pixelzoom if that was the plan, lets follow it, ie dev test first. |
I created the QA issue for dev testing 1.3.0-dev.1, see phetsims/qa#573. Creation of the dev version is deferred until that issue pops to the top of "Active Tests" in the QA Pipeline. |
1/14/2021 PhET-iO meeting: The current milestone is to have 1.3 published by 3/31/2021. I recommended getting the sim into the QA Pipeline by early February to meet that milestone. The sim is a priority for the client. |
From the previous comment:
It's now early February. I'm unclear about who is managing the QA queue, and I'm waiting for someone to tell me when to start the QA process. So assigning to @amanda-phet and @kathy-phet to tell me when to begin. See unchecked items in #251 (comment) for a reminder about what needs to be done. We need to get through a full dev test and a full RC test for |
Milestone was changed to 4/30/21 in the Project Overview, adjusting in this issue. |
In Slack on 3/19, @kathy-phet said:
I had other higher-priority work this past week. And it was unclear whether any of the "blocks publication" issues (6 currently) should block NS. So I was not able to prepare NS for QA before my vacation. Let's adjust the date, preferrably April 5 or later. |
4/5/21: Dev testing started with 1.3.0-dev.1. The QA issue is phetsims/qa#636. |
At 4/8/21 Q2 planning meeting, dates were reviewed. We're still optimistic that we can publish by 4/30/21. |
4/13/21: Dev testing completed with 1.3.0-dev.1 in QA issue is phetsims/qa#636. RC testing started with 1.3.0-rc.1. The QA issue is phetsims/qa#641. |
4/23/21: 1.3.0-rc.1 testing completed. We'll need another spot-check RC. |
4/28/21: Published 1.3.0-rc.2, with QA issue phetsims/qa#643 Immediately noted that the Diff Wrapper is still broken, https://github.com/phetsims/phet-io-wrappers/issues/405 |
Yes, another error about using the diff wrapper from a server, tracking in https://github.com/phetsims/phet-io-wrappers/issues/414 |
I tried publishing an RC.3 and RC.4, but failed both times because of phetsims/chipper#1022. I reverted back to rc.2 to keep the version numbers the same. No RC.3 yet though. I'll ask slack if someone can kick off an RC for me from a mac. |
I'll handle publishing the next RC. |
4/28/21: 1.3.0-rc.2 testing completed. Published 1.3.0-rc.3, with QA issue phetsims/qa#644. The sole purpose of this RC is to verify #271. |
4/28/21: 1.3.0-rc.3 testing completed. 1.3.0 production deployed: |
@kathy-phet This is ready for delivery to the client. Please note the delivery date here. Then assign back to me, so I can update phet-io/doc/partners.md. |
6/10/2021 phet-io meeting: When PhET-iO publications were put on hold to address "migration issues", @kathy-phet decided not to deliver the 1.3 version to the client. It's noted in the PhET-iO spreadsheet, but we'll wait for the next version (1.4) to deliver to the client. Closing. |
From #208 (comment), the plan for the 1.3 release is:
Next step is to establish dates. Assigning to @amanda-phet to lead.
The text was updated successfully, but these errors were encountered: