You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
Announcement
Zikula Core 1.4 Release Candidate 4 is available as of today, 9 July, 2015.
Immediate testing is encouraged. You may download the RC from our links at zikula.org. Release testing guidelines may be found in the Core wiki. Installation and upgrade documentation can be found in the /docs directory.
Our Quality Assurance cycle, explained also in the Core wiki, will be followed in order to achieve our General Release. Please register your vote on the promotion of this build in the promotion ticket.
Please report all bugs and concerns to our issue tracker on Github. Please understand that bugs will not necessarily halt the release of this build. Bugs may be fixed or postponed to another release.
Zikula Core 1.4.0 is intended as a transition release between the very popular 1.3.x series and Zikula Core 2.0.0. While maintaining nearly 100% backward-compatibility, 1.4.0 lays the foundations of Symfony, Doctrine, Bootstrap, Font-Awesome, jQuery and Twig which will be the basis of future development. A new namespaced module structure is established that will be the new standard for 2.0.0 extensions as well as providing many new tools and features to make your site exceptional.
The text was updated successfully, but these errors were encountered:
Please test build #646 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.
Announcement
The text was updated successfully, but these errors were encountered: