Personal tools
  • We're Hiring!

You are here: Home Community Minutes Conference Calls 2011 2011-10-11 Tuesday Meeting

2011-10-11 Tuesday Meeting

Attending: Josh, Melissa, Chris, Elwood, Jean-Marie, Ola, Simon, Andrew, Carlos

Agenda

Remember: Agenda must be complete (with estimated times) on the day before the meeting. Any additions after that must go at the bottom (AOCB)

  1. Accepting minutes from last meeting

  2. Introduction - Mark Hiner from LOCI

  3. Matters Arising (<10 mins)

    • Andrew: Waiting to confirm sizes Done (ASCB: 3'8" (1.1 m) high by 6' (1.828 m) wide, GRE: A0 Portrait)
    • Chris: Nuke RD down.
    • Will is going to merge two ‘collaborative movie’ tickets and make one movie about collaborative work and tagging all together.
    • Chris is going to work on #6779 to get this story finished.
    • J-M is going to extend Sprint 6 to go side by side with 7. Done
    • Everyone: People should push to their own branch then do Pull Request, then we will exactly know what do we want to push to release.
  4. Release 4.3.3 Status (20 mins)

  5. Git/Github status (20 minutes)

    • ticket 6935
    • Synchronization from github to ome.git
    • Branch usage summary
    • Merging of pull requests.
  6. Any other business (<5 mins)

Attending

  • Josh, Melissa, Chris, Elwood, Jean-Marie, Ola, Simon, Andrew, Carlos (14:33)

Notes

  1. Accepting minutes from last meeting

    • Accepted
  2. Introduction - Mark Hiner from LOCI

    • TABLED until next week.
  3. Matters Arising (<10 mins) Started at 14:32

    • Andrew: Waiting to confirm sizes Done (ASCB: 3'8" (1.1 m) high by 6' (1.828 m) wide, GRE: A0 Portrait)
    • Done, com[litely different shape
    • Chris: Nuke RD down.
    • Chris spoked to J Monk on Friday.
    • Will is going to merge two ‘collaborative movie’ tickets and make one movie about collaborative work and tagging all together Done.
    • Chris joined two tickets together and marked one as invalid.
    • Andrew: all existing movies are up. ticket passed back to Will.
    • Chris is going to work on #6779 to get this story finished.
    • Several whiteboard changes.
    • Product and Feature page are open
    • Chris handled all the other tasks.
    • ticket 6729 (imagej install) is closed. Information on download page.
    • Trying to prevent duplication.
    • Several other things for Will #6779 Done (apart from Insight-Annotation movie).
    • J-M is going to extend Sprint 6 to go side by side with 7. Done
    • J-M: We cannot add again another week.
    • Chris: everything on movie front should be done.
    • Movie creation plan (Colin) is still open. This can easily be moved to the next milestone.
    • Some tickets are for 4.3.3. Need to be moved.
    • Everyone: People should push to their own branch then do Pull Request, then we will exactly know what do we want to push to release.
    • Later discussions.
  4. Release 4.3.3 Status (20 mins)

    • Cleaning up 4.3.2 tasks: 20+ as of 1PM UK
    • Chris cleaned up stories. A few things need to be resolved.
    • Remaining tickets from Hic, Emdb tackle as we move forward.
    • Only 11 thing left in the sprint.
    • ticket 6487 Andrew is going to make a draft email for Thursday.
    • Josh: Elwood, Simon, Hic tickets can we moved to 4.3.3
    • J-M:In 4.3.2 there should be only tickets related to documentation and movie. The other tickets should be removed after the meeting.
    • time estimate for 4.3.3 tasks: 20+ as of 1PM UK
    • ReleaseProcess
    • Notes
    • J-M currently 18 top tickets and 1 story. Basically 22 tickets there. General feeling was doing 1 sprint, but realistically we will not be able to release this week. We still need to fix some issues.
    • Won’t do extensive scenario, but will go through each ticket.
    • J-M: What is general feeling about releasing next week?
    • Chris: depends. The web tickets are hard to evaluate. Until we merge the branches, we won’t know. At least half of the current tickets are “closed” in that they have been committed. Once they are stable they will be merged to develop.
    • J-M: perhaps one week behind where we want to be. We had a limited list, but then several things aross during movies & training.
    • J-M: We can use the extra time to test the github workflow, especially with regards to how to validate the changes.
    • J-M: Could go through the movies like a scenario. E.g. once a month?
    • Chris: Good thing about PR, everybody who is interested has the opportunity to review and comment.
    • Chris: based on the webclient example PR seems to work ok in this particular workflow.
    • J-M: Writing the scenario will take longer then real testing.
    • Josh: Suggestion about process page: we should be somewhere on this page by this time. Code freeze when is exactly?
      • Josh: In terms of testing, I’ve gone through commits one by another and then check if this works
      • Chris: Hopefully people annotated commits and PullRequest to do all best to notify what is going on there.
      • Josh: I certainly didn’t know where to click in many cases.
      • J-M: Ideally would be if we could attached screenshot to guide about testing. Where to go, what to click, etc. Because there is not so many details how to test in tickets
    • Chris: there is not so much choice then looking in (PR 7-web, 8-Insight), then get to the ticket. If you do not understand then go back to the person who made a commit.
    • Chris: J-M made significant changes to scripting UI. Will also made changes to scripting UI in webclient. We should go to the scope of out traditional BugFixes only. Those UI changes cover mostly look and action. We have to take testing on board.
    • Josh: do we want to have scripting testing story?
    • J-M: there are 2 tickets assign to Scott which cover those changes. Maybe 10-15 formats to test.
    • Melissa: 4.3.3 looks ok, there is nothing outstanding. I should be able to deliver those changes as the first thing tomorrow.
    • Chris: when you do that merge, can you send what is the exposure of each of the changes is, how to make a testing.
    • Melissa: I will send a list of changes to nit-pick like last time.
    • Josh: Ldap changes. To a certain extent, it was tested by Chris Wood. We need to have upgrade page from 4.3.2 to 4.3.3 because of the ldap changes.
    • J-M: do you want to make a similar testing for LDAP, like last sprint, or is not necessary.
    • Josh: I can’t decide. depends on resources.
    • Elwood: scenario took a day to get everything setup.
    • Chris: In terms of the scope, what kind of modifications we are telling about.
    • Josh: All comes down to testing user filter applied on login. One person requested that but community refused those changes. In 4.3.3 this implementation is configurable.
    • J-M: the person who requested, did actually tested it?
    • Josh: It seems that people use LDAP plugin heavily. It depends on the resources and person testing we might test it locally.
    • J-M: Releasing sometime next week. * Don’t add anything unless it’s a blocker.
      • Chris is away since Wednesday.
  5. Git/Github status (20 minutes)

    • ticket 6935
    • Josh: As commits git merge ome synchronize it with github. Tomorrow hopefully we will start to merge things in. In synch job you can see details. Then all changes appear on trac.
    • We have talked about PR. Is everyone keep comfortable with all the concept of PR?
    • Ola: on webclient side we are ok.
    • Chris: if you are not participating (“@username”) you don’t get comments.
    • J-M: What is the best strategy to answer someone else question?
    • Chris: For Andrew - ome.git on necromancer is read-only
      • J-M: 4.3.3 grew much more, need to establish policy of how long we wait for feedback on PR
        • J-M: also telling people where to click to review commits
      • Josh: for the people who aren’t involved in PR, how do we tell people what they need to people to test.
      • Ola: For people who didn’t push anything, you need to be careful how you create a branch. Any commits pushed to a branch are added to a PR. (Chris: positive and negative at the same time. Ola: both Will and Ola were both surprised. Keep it in mind.)
      • Andrew: Whenever we do testing, we will no longer get email which server you should test against, correct?
        • J-M: In the ticket scenario there has to be specific description which action should be taken to really test the issue. going through the standard scenario does not cover proper testing. Bugs mostly came on the specific/edge use cases.
        • Chris: trying to streamline testing for branches before everyone is working from it. Advantage of Pull Request is that we can look at that code with a framework for commenting, etc. Just currently don’t have a lot of infrastructure yet.
        • Simon: more like agile testing.
        • Chris: Initial filtering is going to happen by the people who understand/designed that code.
        • Chris: If UI has changed so significantly there will be a time when we go through the general scenarios. * Jean-Marie: A patch with a new method in some service will have to have tests before its integrated.
        • Chris: Hopefully, this will make code more stable while is developed. * Josh: I am happy :)
  6. Any other business (<5 mins) * Josh: I do not have anything from maning list or forum

Action Items

  • Scott: create scripting testing story
  • Melissa: merge and send email to nitpick about exposure of changes on Wednesday.
  • Elwood: test ldap changes.
  • Chris: handle Upload/Download OME-Tiff
Document Actions