QA testing for release of Core 1.3.2 build #87 #268

Closed
ghost opened this Issue Feb 16, 2012 · 6 comments

Comments

Projects
None yet
4 participants
@ghost

ghost commented Feb 16, 2012

Please test build #87 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. 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.

@ghost ghost self-assigned this Feb 16, 2012

@MrMontesa

This comment has been minimized.

Show comment Hide comment
@MrMontesa

MrMontesa Feb 17, 2012

Me again!
On renaming any module (display name or module url), no matter if system module or 3rd party added later, I get the follwoing error message in the red alerter box:

Error! The action you wanted to perform was not successful for some reason, maybe because of a problem with what you input. Please check and try again.

But changes are done as expected. The renaming was successful.

Me again!
On renaming any module (display name or module url), no matter if system module or 3rd party added later, I get the follwoing error message in the red alerter box:

Error! The action you wanted to perform was not successful for some reason, maybe because of a problem with what you input. Please check and try again.

But changes are done as expected. The renaming was successful.

@ghost

This comment has been minimized.

Show comment Hide comment
@ghost

ghost Feb 17, 2012

@MrMontesa Please open this as a separate issue.

ghost commented Feb 17, 2012

@MrMontesa Please open this as a separate issue.

@hvorragend

This comment has been minimized.

Show comment Hide comment
@hvorragend

hvorragend Feb 17, 2012

Contributor

Tested a fresh installation and an upgrade. No problems found.

+1

Contributor

hvorragend commented Feb 17, 2012

Tested a fresh installation and an upgrade. No problems found.

+1

@tfotis

This comment has been minimized.

Show comment Hide comment
@tfotis

tfotis Feb 18, 2012

Member

Tested a fresh installation.... No problems found.

+1 from me too.

Member

tfotis commented Feb 18, 2012

Tested a fresh installation.... No problems found.

+1 from me too.

@matheo

This comment has been minimized.

Show comment Hide comment
@matheo

matheo Feb 19, 2012

Member

The stuff works as expected
+1

Member

matheo commented Feb 19, 2012

The stuff works as expected
+1

@ghost

This comment has been minimized.

Show comment Hide comment
@ghost

ghost Feb 19, 2012

Ok then we have a release. Thanks to everyone who participated.

ghost commented Feb 19, 2012

Ok then we have a release. Thanks to everyone who participated.

@ghost ghost closed this Feb 19, 2012

This issue was closed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment