Next Tiki 13 release "scrum" meeting

Tiki13 is now being prepared for the release. Once Tiki 12.1 is released, we are then ready to create the 13.x branch, and then the first alpha for Tiki 13 can be released shortly after this branching, and aim is to have final release by second week of June. The release coordinators are Bernard Sfez and Nelson Ko.

Since this is just after the LTS, it is expected to have a lot of enhancements (like Tiki4 and Tiki7). In fact, current estimates of development planned will make it the release with the most development ever (in terms of developer hours)!

To take advantage of new features from PHP 5.5, as recommended by a member of the PHP core team, we will make this the minimum requirement. Even if PHP 5.5 is quite new and still has a very small market share, it will be much higher by the time Tiki 13 is released (April 2014). Also, a big part of our community goes from LTS to LTS and thus, will only start upgrading to 15.x in the later part of 2015 and 2016, by which time PHP 5.5 and up will be quite common.

Documenting of Upgrading Issues

Please document those at https://doc.tiki.org/Tiki13#Upgrade.

Latest Update

As of June 27, I have finished upgrading dev.tiki.org to Tiki 13.

Themes.tiki.org is the very next one (will do it tomorrow morning). If all is well, doc.tiki.org will follow in a few days.

Unless serious problems are discovered with the upgraded dev.tiki.org, I will also be proceeding to releasing Tiki 13.0 beta over the weekend, once I've upgraded themes.tiki.org.

I will send a message about temporary commit freezing before commencing tagging and packaging of Tiki 13.0 beta.

Testing on nextdoc.tiki.org

Steps that need to be done on other tiki.org sites before upgrading

The following can and should be done before upgrading.

• h3 in shared footer custom need to be changed to h4
• Logo source should be changed from previewxxx to dlxxx (so that it shows without dithering)
• You should set Containing Class in Admin...Modules (Appearance tab) for the Topbar search module to "col-md-3"
• You should set Containing Class in Admin...Modules (Appearance tab) for the Topbar menu module to "col-md-9"
• Remove under Admin...Look and Feel (Customizations) any custom CSS except

.twfooter .box {width: 106px; float:left; text-align: left;margin-left: 30px;}
.twfooter .box:first-child {margin-left: 0;}
.twfooter img.externallink {display:none;}

Opinions on side column widths?

• IMO the left and right columns may be too narrow (currently the column width proportions are 20%-80%-20%). I think maybe switching to the 25%-50%-25% layout template might be better (although that would make the center column considerably narrower) .

Nelson to gezza: I am trying to see how to rename the layout labels without actually renaming the layout itself (because too risky at this stage right?) IMO,
Basic -> Standard Bootstrap
Classic -> Classic Tiki
Three Containers ->
Three Containers with 3-6-3 Columns

• Internal
• Jquery Mobile
• layout_plain.tpl

Social
"* means for internal system use only"
- classic layout supports shadows, basic does not.

Things to test in general (any new or test upgraded Tiki)

If you are testing, please write down what was exactly tested below so others can refer. Thanks.

• Registration in its various forms (depending on email/admin validation) and if tracker info is required etc...
• Try creating some articles and editing them
• Try creating forum and use the forum

More details including Video Introduction

Earlier in the year, while development was still in progress, a summary of development work was on this page, now moved to Tiki13Development.

External Libs to Upgrade

See Tiki 13 Composer Dependencies

Featured bugs

• http://dev.tiki.org/item4885 - This one requires a change to support 4-byte UTF8 in MySQL. But this means requiring a certain level of MySQL. Probably should be taken care of in installer.

Regressions

 To who find/report a bug:

1. Test on your website, test on neutral ground demo, test on different version (and log results).
2. Report to the WishList/Bug Report tracker.
3. Give short BUT COMPLETE explanation about the problem. (keep the essential remove the rest).
4. Create an instance so next available Dev will have anything he need to try to solve the issue.
5. Retest regularly with new release and for each test, confirm your input. Change date and improve explanation.
6. Answer to the Dev request.
7. Log any changes and mark as solved IF RESOLVED (pleassssseeeee).

   
   

Open

• «
• 1 (current)
• 2
• 3
• »

Pending

Closed

Blockers

Wishlist item categorised as "Blockers" (non-specified versions) - status open or pending.

• «
• 1 (current)
• 2
• »

Other 13.x bugs

Other Open

• «
• 1 (current)
• 2
• 3
• 4
• »

Other Pending

Other Closed

Upgrade

Upgrading to Tiki13?

See notes here:
https://doc.tiki.org/Tiki13#Upgrade

2 pages link to Tiki13

• Using Less CSS with Tiki
• Zend Framework

  
  
  

• release process 13