QA testing for release of 1.4.4-rc6 build #182

[zikulabot]

Please test build #182 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 three +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.

[Guite]

changed voting threshold from five +1 votes to three

[craigh]

please consider voting @rallek @Kaik @gfr @rmburkhead @nmpetkov @cmfcmf @jusuff @matheo @tfotis @shefik @phaidon @espaan @marcpare4 @trichers @ccandreva @rojblake @paustian @MrMontesa @Portugao

[rallek]

as I tested in the past a lot and my upgrade went fine again with RC6 I vote +1. I will do some more tests tomorrow but I do not expect a blocker in my environment and usecase so far.

[MrMontesa]

Any reason why this got closed?

[rallek]

It is released

[MrMontesa]

Indeed, but havent seen 5 nor 3 up-votes. Wodering why we have a nice process defined, when no one seems to care...
Must be for a good reason that is hidden to me.

[Guite]

@MrMontesa due to missing response activity we need to slightly adapt the process. Thus, we are going to introduce something like "requires X up votes OR Y days without Z down votes". We are not sure yet about the details though.

[craigh]

there were three up votes. rallek, craig, axel.