Volunteering Facilitator: Bernard Sfez / Tiki Specialist

When

Time in your timezone (when this page was last reloaded): Monday 22 July 2024 19:26:54 UTC

Time was set by participants vote: See history

Thursday, November 23rd, 2017 at 14:00:00 UTC time (click for time zone in your city)

What

See Roundtable Meetings for a detailed description.

Fixing Community Items session

(Why this?)
Closing the Roundtable time we use available time to organize a session to fix a list of bugs from the reports at https://dev.tiki.org/Community+items#Summary and https://dev.tiki.org/Community+items#List

• ...

Tiki community issues (no coding) where volunteers are needed

• ...

Where

http://live.tiki.org

Topics

1st hour quick news

1. Tiki 18 release process -> branching
2. TikiFestFosdem2018 - can we confirm dates yet?
3. ...

Second hour, longer topics

1. If not completed or scheduled, branching should be done
2. changelog.txt nomore generated anywhere - makes it sense to still use the commit [TAG]s?
3. ...

Recording

• https://recordings.rna1.blindsidenetworks.com/citadelrock/d559965849921585c1849af03b7a51638700d979-1511443660203/presentation/?t=00m00s

Follow-Up

Post-branching Checklist

Taken from https://dev.tiki.org/How%20to%20release#Post-branching_operations

1.1.1. Post-branching operations

1.1.1.1. Update $profilesLink

• ✔ In lib/setup/wiki.php, update $profilesLink to the new branch

1.1.1.2. Make new profiles

• Contact the Profiles Team to ask them to make new profiles.

1.1.1.3. dev.tiki.org

• ✔ Create branch page. i.e.: Tiki18
  • (?) Move the current alias from the old branch to the new created one
• ✔ Add the branch as an option for the Tiki Version field in the Bugs & Wish list tracker
• ✔ Update Daily Build (You need to ask Oliver Hertel to add new versions)
• ✔ Update Get code
• ✔ Update Where to Commit
• ✔ Update Semi automatic merging period

1.1.1.4. show.tiki.org

• First add the new branch to the dropdown in templates/trackerinput/showtikiorg.tpl
• Remember to backport to the version that the actual dev is running
• in the show server checkout the new branch into usr/local/src/tiki
• in the show server add the branch to /usr/local/sbin/tim-common BRANCHES="trunk 12.x 13.x"
• Refresh the instances by calling right away the cron: /usr/local/sbin/tim-cron
• Once dev.tiki.org updates, it should then work.

1.1.1.5. demo.tiki.org

• Create a site for new version

1.1.1.6. Pre-dogfood servers

• Each tw:Pre-Dogfood Server should be moved from trunk to the next branch and each site should go through at least 30 minutes of manual testing of the most common operations.
  Ex.: on http://nextdev.tiki.org, someone should try to report a bug, or on http://nextdoc.tiki.org try and add a new page to a structure (even though it all will be overwritten the next day).
  • the instances need to svn switch and refreshed immediately, e.g.
    +svn switch https://svn.code.sf.net/p/tikiwiki/code/branches/13.x .
    +sh setup.sh -n fix
    +php console.php database:update
  • /usr/local/bin/refresh-nxt.sh needs to be updated so the next cron switches to the right branch
  • A couple of days before the release the cronjob to do a full upgrade including DB-sync from live sites must be disabled so that designers and gardeners can test/learn/prepare for the upgrade of the live community sites.
  • After release the /usr/local/bin/refresh-nxt.sh needs to be changed to trunk again and the full upgrade cron job reenabled.

Chat log

Pages related to this one

One page links to Roundtable Meeting 2017 11

• Roundtable Meetings