Difference between revisions of "WBConfCall 2017-07-20-Agenda and Minutes"

From WormBaseWiki
Jump to navigationJump to search
Line 61: Line 61:
 
***Would like time to track down and address the problem
 
***Would like time to track down and address the problem
 
*WS261 is nearly done, though
 
*WS261 is nearly done, though
*We should then delay the upload for WS262 or we will be in perpetual catch-up mode
+
*Should we then delay the upload for WS262 or we will be in perpetual catch-up mode
 
*Todd suggests we push all releases back
 
*Todd suggests we push all releases back
 
*Kevin proposes a slightly longer, five-week build cycle to accommodate having to build Datomic database, as well as ACeDB
 
*Kevin proposes a slightly longer, five-week build cycle to accommodate having to build Datomic database, as well as ACeDB

Revision as of 15:55, 20 July 2017

Agenda

Release Announcements

  • maybe we can restart announcing our releases outside of staff@wormbase

WS260 Website Release

  • Possibility to delay WS260 website release to Aug 25 (currently scheduled at Aug 4)?

New Datomic Widgets on Staging

  • Testing needed for:
    • construct (Karen - responded)
    • interaction
    • pcr_product
    • phenotype
    • paper (Kimberly - responded)
    • position_matrix
    • pseudogene
    • rearrangment

Open Help Desk Tickets

Minutes

  • On call: Adam, Chris, Daniela, Gary, Juancarlos, Karen, Kevin, Kimberly, Michael P., Paolo, Paul S., Ranjana, Raymond, Scott, Sibyl, Todd

Release Announcements

  • In response to some user feedback at the worm meeting, shall we announce our releases outside of WB staff?
  • Ideas:
    • Blog
      • Rotate turns on the blog?
      • Blog could link to the more detailed report of release statistics
      • Rotate authorship between Hinxton and Caltech
      • The blog post doesn't have to strictly correspond to the release date, but would record the release date for reference
    • Forum
    • Mailing lists
      • wormbase-announce
      • should resurrect the announce list
    • Website banner
  • Whatever we decide, this would need to be initiated by OICR
  • Suggestions for release email
    • Make the email more of a narrative with a link to the statistics, lists
    • For the narrative, capture what has been accomplished, substantially, in the latest release
      • Provisional version could be posted for comments
  • How critical is it for people to know the exact date the release is made live?
    • It is important for people to cite/note versions that they searched
  • Is there a REST endpoint for determining exactly when a release went live?
    • Todd will look into this; may exist, but if not, can be easily made

WS260 Website Release

  • May need to be delayed for three weeks past scheduled date
  • Why?
    • Datomic database was not available until yesterday
      • Datomic database is not available until after the official ACeDB release
      • Datomic has only recently been considered formally part of the production cycle
      • The web developers need a full development cycle to test Datomic, though
    • Also noticing some unresponsiveness on the website
      • Would like time to track down and address the problem
  • WS261 is nearly done, though
  • Should we then delay the upload for WS262 or we will be in perpetual catch-up mode
  • Todd suggests we push all releases back
  • Kevin proposes a slightly longer, five-week build cycle to accommodate having to build Datomic database, as well as ACeDB
    • This proposes that we move the data upload one week ahead; the overall cycle would still be eight weeks
    • One week is enough to build Datomic?
    • But there are still some problems with the data models in Datomic and we can't predict what these issues might be
  • Should the release letter (currently sent out) be coordinated with the ACeDB or Datomic database build?
    • Who needs to be alerted to the release?
    • Doesn't appear to affect Caltech who use automated SOPs to check ftp site daily