Closed avas27JTG closed 10 months ago
@hanzei @DHaussermann I'm wondering your thoughts on if we need a release test on this, besides the step we recently added to ensure the build runs properly on a Cloud server. cc @AayushChaudhary0001
I'm fine with skipping release testing on this one.
I'm fine with skipping release testing on this one.
Cool, I'll add the QA to the pipeline and we can do it whenever we get available bandwidth
Cool, I'll add the QA to the pipeline and we can do it whenever we get available bandwidth
@avas27JTG I'm not sure exactly what this means. Do you mean specifically my comment about "the step we recently added to ensure the build runs properly on a Cloud server"?
Cool, I'll add the QA to the pipeline and we can do it whenever we get available bandwidth
@avas27JTG I'm not sure exactly what this means. Do you mean specifically my comment about "the step we recently added to ensure the build runs properly on a Cloud server"?
@mickmister I meant that once we are sure that it runs properly on cloud server we can perform a QA sanity to proceed with the actual release following point 5 Perform release testing
of the release process.
Please let me know if we want to skip QA sanity and just cut the actual release if it works well on Cloud Server.
@avas27JTG I've confirmed this runs correctly on a Cloud server. Merging the PR since the change is minuscule
Summary