...

Since we are dealing with a standard release we must follow the procedure for OpenMI standard releases. So far we do not have such procedure formally accepted by the OAEC. On this agenda (point 4.1) is a proposal for a procedure. So, let's discuss this first and then see how we can fit some dates into this.

Minutes:
with respect to version 1.4.1 release, we will go into beta by the next OATC meeting in Delft, and a release on December 20 th 2008. Everyone in encouraged to start using the GUI version 1.4.1 now.


Version 2:

OATC Meeting November: Configuration finished. Draft for Spatail and return types.

OATC Meegting January 09: Cut off meeting, kick out things cannot achieve.

OATC Meeting March: SDK, Standard, and GUI in beta version.

OATC Meeting June 09: Tested real models finished, submission of the standard to the OAEC:

Review period (4 months)

Update period (3 months)

Release in December 2009.

3. OpenMI Java and OpenMI .net synchronization

...

From Jan: I have at task from one of the previous OpenMI Association Executive Committee meeting to elaborate a proposal for OpenMI Standard release procedure. These procedures will define the rules for how to go from OpenMI Standard release version x to OpenMI standard version x+1. I think that the OpenMI standard it selves is the most important asset of the OpenMI Association, which also means that rules for how this standard may be change becomes very important. I thought a lot about it (apparently, more difficult that I first anticipated), and I *Minutes:*have

now written my first idea down in draft form. I would appreciate if we, at the OATC meetings, could discuss these ideas.
Please review the Proposed procedure for OpenMI Standard releases.

...