-
Notifications
You must be signed in to change notification settings - Fork 66
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
QA testing for release of 1.4.4-rc1 build #152 #3225
Comments
I vote 👍 |
I cant re-activate my extensions with that build after upgrading from 1.4.3. Filed #3226 to confirm |
I cannot vote for now because of #3227. |
Changing my vote to 👎 due to #3231 and #3212 (both of which are now fixed) #3226 is pending confirmation but would be a blocker if confirmed. ping @MrMontesa #3227 is not a blocker as there is a workaround (turning off the asset merger) |
I vote 👎 because of #3231 . |
Please test build #152 and decide if it should become the next official release.
Anyone may participate in the testing process.
Testing guidelines can be found in Release Testing Guideline
We require five +1 votes to promote this build and a minimum testing period of three days testing before the build can pass.
Two "-1" votes (with reason) will cause us to fail the build. If this build fails, votes cannot be transferred to
the new release candidate, testing must resume from the beginning.
Please do not report bugs in this ticket, only register your approval or disapproval. You must give a reason and
reference if appropriate (e.g. link to a ticket) for negative votes.
Please report issues in a separate ticket.
Notes, References, and/or Special Instructions
Do not vote negatively if you find non-release blocking bugs. Minor and major bugs may be scheduled in a future version.
The text was updated successfully, but these errors were encountered: