-
Notifications
You must be signed in to change notification settings - Fork 67
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 Core 1.3.2 build #85 #267
Comments
I'm not 100% familiar with testing and bug reporting. Specially for QA. The only thing I recognized is: Can someone confirm? |
What version of Profile appears in the download? Maybe the build is |
In which download? |
I am referring to these files: http://ci.zikula.org/job/Zikula_Core-1.3.2 |
Ahh ok, I've downloaded built85 as requested. The core_min thingy is a little bit different. I removed all info about that from my origin post, since it points into a wrong direction and is independent from the QA testing. Sorry for that. In fact what I did was:
Additional info about core_min that does not belong to QA testing.
|
@MrMontesa so are you saying that Profile 1.6.0 fails, but Profile 2.0.0 works? /cc @rmburkhead |
-1 this build has failed. This commit isn't included in build #85 so when you try to install Profile, it fails |
Failing build. |
See next build in #268 |
Please test build #85 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.
The text was updated successfully, but these errors were encountered: