Difference between revisions of "WBConfCall 2020.05.21-Agenda and Minutes"

From WormBaseWiki
Jump to navigationJump to search
 
(One intermediate revision by one other user not shown)
Line 1: Line 1:
 
==Agenda==
 
==Agenda==
 +
 +
=== WS277 release ===
 +
the WS277 release will be delayed another week (pre-FTP release 29th of May / 5th of June on FTP)
  
 
=== WS278 Models and Build Schedule ===
 
=== WS278 Models and Build Schedule ===
Line 15: Line 18:
 
** User asking for tool to visualize location of list of genes on the genome
 
** User asking for tool to visualize location of list of genes on the genome
 
** Original question/request in 2013, follow up in 2015, now second follow up in 2020
 
** Original question/request in 2013, follow up in 2015, now second follow up in 2020
 +
 +
==Minutes==
 +
 +
===Release scheduling===
 +
*WS277 build will be delayed another week, due to unexpected changes to the Sanger compute farm
 +
*More broadly, if the Hinxton build is late the final production release date will nominally be delayed by the corresponding amount of time (and communicated to users). The CalTech upload date for the next release will also be shifted (and communicated to curators).
 +
 +
===Helpdesk===
 +
* https://github.com/WormBase/website/issues/7714
 +
**A feature like this used to exist in GBrowse. Scott will take a look and reply to the user.
 +
 +
===AOB===
 +
*Scott is planning a webinar on data browsing in JBrowse. Will circulate content. Looking for a helper.

Latest revision as of 12:38, 22 May 2020

Agenda

WS277 release

the WS277 release will be delayed another week (pre-FTP release 29th of May / 5th of June on FTP)

WS278 Models and Build Schedule

  • Confirm model proposals and changes
https://github.com/WormBase/wormbase-pipeline/releases/tag/models.wrm.WS278
    • Genotype/Disease_model_annotation
    • ECO_term
  • Confirm build schedule
    • As proposed on the #build278 slack:
Rather than our current fixed dates schedule, I suggest we move to a sliding release schedule: the public release to production would occur no later than two months after whenever the build is released, or whenever things are ready.  That is what we had agreed on at the last conference call. We can still publish anticipated release dates, in part because it helps relieve the agony of deciding on dates for each and every release.  And still strive for 5-6 releases a year.
    • What does everyone think?

Help Desk

Minutes

Release scheduling

  • WS277 build will be delayed another week, due to unexpected changes to the Sanger compute farm
  • More broadly, if the Hinxton build is late the final production release date will nominally be delayed by the corresponding amount of time (and communicated to users). The CalTech upload date for the next release will also be shifted (and communicated to curators).

Helpdesk

AOB

  • Scott is planning a webinar on data browsing in JBrowse. Will circulate content. Looking for a helper.