Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

https://tulibdev.atlassian.net/browse/MAN-998

https://tulibdev.atlassian.net/browse/MAN-1012

https://tulibdev.atlassian.net/browse/MAN-1026

Date

Attendees

Agenda

Notes, decisions and action items

- Sprint Kickoff

Steven Ng Chris Doyle Brian Hoffman (Unlicensed)

Jira Legacy
serverSystem JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId72190e5c-ce35-3f39-b915-64292d694deb
key
  • theming issues

  • populate both the rich text fields and its draftable counterpart

  • Will need to do a migration

  • Steven and Chris will work on detail

  • WYSIWYG - with Steven now

Jira Legacy
serverSystem JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId72190e5c-ce35-3f39-b915-64292d694deb
key
  • Chris can go back to this

  • tests are failing because of instance variables

  • Brian will take a look at it

Jira Legacy
serverSystem JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId72190e5c-ce35-3f39-b915-64292d694deb
key

The ePub reader will require a new server which will require work on a devops sprint in January.

  • a few options were looked at

  • Readium out of Berkeley - very accessible

  • would need to run as its own app

  • we could use one server for both TUpress and manifold

Same as above

Steven

  • Deploy problems after the skylight merge

    • Reverted merge - gems may need to be cleaned up.

  • Getting testing cleaned up for trix editor

Brian

  • started looking into performance issues

    • a lot of ruby CPU - Prod 2 usage is 5x higher than prod-1

  • set up vagrant deployment

  • point it at datadog to figure out why the two server are acting differently

  • vagrant creates a portable QA

  • add to playbook to automatically pull from database

  • enable rich text drafts in playbook before deployment

    • Ticket created for this:

      Jira Legacy
      serverSystem JIRA
      columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
      serverId72190e5c-ce35-3f39-b915-64292d694deb
      keyMAN-1036

Chris

  • Started investigating administrate on the backend