Overture Tool

Formal Modelling in VDM

Overture Tool

Go to our GitHub Profile

Follow @overturetool

Net Meeting 74

   
Date Sunday the 27th of October 2013 at 13:00 CET
Participants PGL (chair), NB, HS, JC(partially present), JF(partially present), SS

Review Status of the Action List

The action item list is maintained as a tracker on SourceForge.

Overture Language Board Status

Minutes of the LB NM, 13th October 2013

Status of VDMTools Development

newest version

The VDM++ Toolbox v9.0.3 - Mon 30-Sep-2013 11:06:15 +0900

Status of the Overture Components

VDMJ

The following changes were made since the last NM. I’m still applying changes to Fujitsu’s command line “VDMJ” and PJ is applying the corresponding changes to the 2.x.x branch of Overture. Note that two recent LB RMs are now available (“stop” statements and sporadic threads), though the new keywords for both of these need to be declared in the Editor (ie. I’ve only changed the interpreter, not the editor, so “stop” and “sporadic” are not yet highlighted keywords).

2013-10-22 Corrections to type check of static operation guards\ 2013-10-21 Correction for sync guards on static operations\ 2013-09-30 Correction for two successive stop calls\ 2013-09-27 Correction for deadlocked CT test cases\ 2013-09-26 Correction to stopped thread handling\ 2013-09-26 First cut of RM#18, sporadic threads\ 2013-09-26 First cut of RM#20, thread stop statements

Other component

Development Board Status

Reference to Development Board

Release Planning

Overture 2.0.0

Overture 2.0.0 is up on sf.net, but the release hasn’t been announced yet. We still need to:

  1. Run down the bug list, closing those that are definitely fixed
  2. Make the release note
  3. Update the web pages
  4. Upload the Overture Eclipse Plugin repository (so that pure Eclipse users can install it in a general environment)
  5. A “grand renaming” of branches in the git repository to clean things up (v2 is the “astv2” branch, and that will become the “master”+”development” branches; v1.2.x is on the “master”/”development” pair, and will be moved to something more appropriate). A warning email will go out beforehand.

This is, as usual, constrained by my time (except for the bug list).

At some point in October/November we expect to release a v2.0.2 that includes some cleanups small fixes. I will need to run down the commit log to see what’s changed, but there have been significant changes that to support aspects of COMPASS, and some of them may be more general. One of the things I hope to have set up for the 2.0.2 release is code signing for the OS X binaries.

Overture 1.2.x

I have noted that Nick has made some fixes to that branch. I would like a clear indication of the plans for 1.2.x going forward.

1.2.5 is is the end of the 1.x.x line.

Buildserver

Still pending my time. (last meeting: We have a new buildserver at AU for the Overture (and derivate projects). It’s still in the process of being configured; it probably needs 1–2 days of effort to move everything over. The switchover should be invisible to most people, however.)

Move to GitHub

The dev board is considering moving all code repos to GitHub (AstCreator is there now). If you’d like to check out what it looks like, go to https://github.com/overturetool/overture and have a look. It is current as of Saturday afternoon (and moving git repositories is really easy). I’m looking into moving the bug tracker as well; I do not have any immediate suggestions regarding the LB tracker, the netmeeting action tracker, or the feature request tracker (though the last could easily be merged into the bug tracker).

Branding — COMPASS and DESTECS

Just a note for general information. The DESTECS Tool is being rebranded as the Crescendo Tool and, similarly, the COMPASS Tool will become the Symphony tool. New icons, web domains, etc, are being created.

Strategic Research Agenda

The Strategic Research Agenda is reviewed every other NetMeeting.

Community Maintenance Reporting

Current Status

See Community Management.

Publications Status and Plans

Also see Planned Publications.

In preparation:

In review:

In press:

Any Other Business

PGL: We need to find out how to improve the attendees for these NMs in general. I think suggestions are welcome.

Next Meeting