Page History

Scott: 

• Deploying 6.3 to DEV
• Tree Updates - resolving issue with Kim
  • Posted files to sftp (lexbig jar and war) to be tested by Kim.
  • Can send client zip if necessary
  • NPO loader is loading correctly.
• OWL discussions with Kevin.

Cory:

• • Agile Planning
    • Configuring JIRA
    • Created all artifacts in JIRA
  • 6.3 and 6.4 documentation
    • Created structure and documents.
  • 6.2 announcement
    • Updates to documentation from Larry.
  • 6.2 documentation API
    • Updated to use a new public server.
    • Published URL is better.
    • Need to update permissions on the Protege server.
    • Heroku hosting site.

Kevin:

• OWL2
  • Reviewing the spreadsheet from Gilberto.
  • 100+ issues in spreadsheet.
  • Need to write testcases to capture each related issue.
  • Time to be spent on testing and regression testing. 
  • There are some common issues, but not absolutely sure that is the case for all.
    
    

Craig:

• Agile
• 6.3 docs
• 6.4 docs
• Closed 6.2 release
• Cleaned up previous versions on Jira

• JIRA will be used to track all Agile artifacts.
• • Jira Versions - Phases of the project
  • Jira Epics - Describes a larger issue or feature to be implemented
  • Jia Issues - Stories which describe the issue or feature to be implemented
  • • Jira Sub-Tasks - Tasks which represent the work to be completed
• Sprints will be used to iteratively develop the stories. (1 to 2 week Sprints)
• • Will be focused on what is agreed upon in each Sprint Planning Meeting.
  • If a new issue or question comes up for the team, it will be put into the backlog (Jira item created) and will only be considered during the next Sprint planning meeting for inclusion in the next Sprint.   
  • Consulting time can be included in the Sprint, but will reduce the effort possible by the team.  
• Scrum meeting flow:  

<image>Image Added

• Retrospective and sprint planning day before sprint starts.   
• • Suggest Sprint starts on Wednesday
  • Sprint and Retrospective planning on Tuesday
  • Wednesday NCI meeting - Demo and Sprint overview OR Backlog Refinement

• Project Roadmap and Agile Reports will be used to report progress.  
• Cannot start Lucene work until 6.3 tasks are complete.

https://lexevscts2.herokuapp.com/cts2

Server configured and linked in the announcement.

LexEVS Project Documents

• Include a note on the 6.3 and 6.4

• that 6.3 is an internal release only.

Scott reviewed what is available for installers. The installer izpack is still most popular (based on review).

Another option is a configured VM that a user could use to get up and running quickly.

VM might not work for all. Would be good option for someone that need to quickly look at and evaluate. Not necessary lack of skills, but immediate need.

Need to wait - on demand from others. Minimally provide more build documentation.