Skip to main content

Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

TPTP-PMC-20090422

Logistics

Attending

  • Paul, Oliver, Chris, Ernest, Joel

Any issues with last week summary?

  • no

4.5.2.1 discussion

Paul wanted to bring up versioning discussion on behalf of Kathy IBM consumer wants version number increment to facilitate updating

  • How will we increment the version numbers for the items in 4.5.2.1
  • We discussed the fact that 4.5.2.1 is not actually a release nor is it planned to be a TPTP release and that ordinarily version numbering only is done at actual releases. It is simply a convenience for the IBM consumption.
  • The proposed solution suggested is to increase the "service digit" of each modified component by 1 for 4.5.2.1 milestones and in 4.6 to increment modified components to the next 100.
    • Also, in 4.6, if there is significant enough change can change the minor digit by one.

One discussion topic was about the overhead of this. This updating of numbers is the responsibility of the project leads at "release" time so

  • there is no additional overhead on development contributors/committers only on project leads.

Another discussion topic revolved around making sure that we do not have mistakes in the protocol resulting in confusing numbering between 4.5.2.1 components and 4.6 components.

  • We talked about the possibility of running some reports of 4.5.2.1 versus 4.6 in addition to current components
  • In looking at reports, it looks like current 4.6 reports are done relative to 4.5 instead of 4.5.2.
  • Some revamp of the reports is desirable
  • There was general agreement that if the reports are working it will help avoid problems in the numbering

There was unanimous approval to using the proposed numbering scheme

4.6 test pass

Joel & Josh working hard to get BVTs into automated build/test side

  • The results will now will be included automatically.
  • JUnit tests are now included automatically for all projects
    • No need to run any junit tests. Action items to leads to roll this down to participants.

Kudos to Joel/Josh from PMC.

Test project has two blocking issues

  • Would like to regenerate a new candidate build today or tommorrow
  • No objections

Misc

Chris is getting quite close to shipping Itanium systems

  • Ernest asked Chris to follow up with him when shipping happens to facilitate logistics in Toronto.

Back to the top