Skip to content
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

Closed
zikulabot opened this issue Nov 28, 2016 · 8 comments
Closed

QA testing for release of 1.4.4-rc1 build #152 #3225

zikulabot opened this issue Nov 28, 2016 · 8 comments
Labels
Milestone

Comments

@zikulabot
Copy link
Member

zikulabot commented Nov 28, 2016

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.

@zikulabot zikulabot added this to the 1.4.4 milestone Nov 28, 2016
@craigh
Copy link
Member

craigh commented Nov 28, 2016

I vote 👍
I tested http and CLI install and upgrade (from 1.4.3)
I also did some other minor testing around.

@Guite
Copy link
Member

Guite commented Nov 29, 2016

ping @rallek @Kaik @gfr @rmburkhead @nmpetkov @cmfcmf @jusuff @matheo @tfotis @shefik @phaidon @espaan @marcpare4 @trichers please help testing and voting for the 1.4.4 release

@craigh
Copy link
Member

craigh commented Nov 29, 2016

@MrMontesa
Copy link

I cant re-activate my extensions with that build after upgrading from 1.4.3. Filed #3226 to confirm

@nmpetkov
Copy link
Contributor

I cannot vote for now because of #3227.
The problem arose somewhere between build 117 and 152, as my previous installed version was build 117, and it worked. I'll test other modules also.

@craigh
Copy link
Member

craigh commented Nov 30, 2016

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)

@Portugao
Copy link

I vote 👎 because of #3231 .
The standard module for simple pages have to be installable.

@craigh
Copy link
Member

craigh commented Nov 30, 2016

@Portugao - please try build 153

closed with two negative votes.

@craigh craigh closed this as completed Nov 30, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

6 participants