We have a Specifications Editorial Committee meeting in Ljubljana 18-20 April, during which we will be processing as many of the outstanding Problem Reports (PRs) as possible.
The agenda is posted on the meeting page.
If members of the community have other issues not covered by raised PRs, e.g. future directions questions, that they would like to be discussed, they may add to the agenda page under the ‘Community Issues’ heading.
We had a very useful SEC meeting in Ljubljana last week. For those interested in the outcomes, see the meeting wiki page and sub-pages, which contain extensive notes. Feel free to add comments to any of these pages.
The next RM and BASE releases are nearly finalised, and we expect to issue RM Release 1.0.4 within a few weeks. You will also see a lot of changed statuses on Problem Reports and RM Change Requests.
Hi Thomas,
Is there some thing to say when the RM Release 1.1.0 approximately will be expected?
Thanks for an indication
Bert
Generally speaking, you can look at the ‘Releases’ page of any Jira project (remember: there is one Jira project for each ‘component’, i.e. RM, AM, SM, PROC, CNF, …) and you will see the dates attached to each release. For RM, it is this view in Jira. We’ll release earlier if we get the work done earlier.
Note that as items get completed within a release, the solution is already a commitment, so if your need is to know ‘how will openEHR solve this problem’, then you can often know the answer some time before the release is actually made - just look at the progress picture for that release. E.g. Release 1.0.4 is pretty far along.