Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Papyrus-RT/Releases/Oxygen v1.0 Release Notes"
< Papyrus-RT | Releases
(Created page with "File:PapyrusForRealTime-Logo-Icon.png<br/><br/><br/><br/><span style="font-family: Helvetica,Arial,sans-serif; font-size: 48px;"><b>Neon v0.9 Release No...") |
(→Known Issues: Prepared the page for Papyrus-RT 1.0 (Oxygen) information, marked as early version) |
||
| Line 41: | Line 41: | ||
{{warning |Path Names| The long-standing pathname issue when installing in deeply nested directories in Windows appears to still be an issue with the Windows installation. If you get errors extracting the RCP archive or running Papyrus-RT, consider installing in a directory closer to the root of your system! }} | {{warning |Path Names| The long-standing pathname issue when installing in deeply nested directories in Windows appears to still be an issue with the Windows installation. If you get errors extracting the RCP archive or running Papyrus-RT, consider installing in a directory closer to the root of your system! }} | ||
| − | And yes, of course, we are painfully aware that there are still issues with the tool. A list of known issues is provided below | + | And yes, of course, we are still painfully aware that there are still issues with the tool. A list of known issues is provided below, with workarounds, when available. |
| − | Note that the descriptions of the known issues, below, are | + | Note that the descriptions of the known issues, below, are summarized from their corresponding bug discussions. |
| − | Bugs are listed from most recent to oldest, with bugs found | + | Bugs are listed from most recent to oldest, with bugs found after the official release indicated with a leading "{{new}}" tag and those updated post-release indicated by an {{updated}} tag. |
| − | ; | + | ; TBD |
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
[[Papyrus-RT/Releases#Papyrus-RT_MVP2_.28v0.9.29_-_Better_behave.21|Back to Papyrus-RT v0.9 Release]] | [[Papyrus-RT/Releases#Papyrus-RT_MVP2_.28v0.9.29_-_Better_behave.21|Back to Papyrus-RT v0.9 Release]] | ||
Revision as of 14:39, 17 July 2017
Neon v0.9 Release Notes
Back to Papyrus-RT v0.9 Release
WARNING: Working version of the release notes! This page WILL CHANGE prior to release!
What have we done!
The best part is that we have finished what we originally wanted to accomplish in MVP2 (and maybe a bit more) -- and we managed to move to Oxygen!
These were the goals we have set for this release, along with what we have done:
- Migrate to Papyrus Oxygen - accomplished!
- This was more work than anticipated, as many changes were done in Papyrus to make it better and more flexible - and that meant we needed to adapt. Luckily, we had great collaboration with the Papyrus team and most of our issues were addressed. As we release Papyrus-RT 1.0, there are still somePapyrus bugs blocking Papyrus-RT that will need monitoring to see about doing something when they are fixed...
- Complete work on hierarchical state machine behaviour - accomplished!
- Improving the usability of the state machine editor for UML-RT was a priority and much work was done to improve this. We have tried and, we believe, achieved in implementing a good user interface for creating and navigating UML-RT state machines (there were so many corner cases in doing so!).
- Complete work on structural Inheritance - accomplished!
- This barrel of
monkeyspoisonous snakeslaughs from v0.9 was emptied and our developers are on the way to full recovery thanks to summer holidays! - There are still a few little quirks (see "Known Issues" ), so we will need to see what can be done in subsequent releases.
- This barrel of
- Complete work on behavior Collaborative modeling (hierarchical state machine compare/merge) - accomplished!
- Many improvements were done with regards to both structure and behaviour compare/merge.
- Complete work on basic support from code snippet view - accomplished!
- The code snippet view is now better integrated into the workflow and available in more contexts. If you want to work in a full-blown, target language-aware editor for, you still need to start a separate view - but that is still functionality for the future.
- Complete work on pervasive default language support - accomplished!
- Target language can now set when creating a model or through the model's properties and is used whenever a target language can be used.
- Complete work on behavior Inheritance - accomplished!
- More monkeys taken out of that barrel...
- Complete work on runtime support - Partially accomplished!
- Some work was done to improve Windows support.
- Some documentation is being added to the wiki to help with command line parameters and debugging commands (which could already be accessed from the command line help).
- Plus, we got all the improvements from the Papyrus Neon.3 release!
- Beta
- We did not do too well with the Beta. We learned our lesson in that an unstructured beta is not the best approach. Next time, we will do better!
Known Issues
Path Names
The long-standing pathname issue when installing in deeply nested directories in Windows appears to still be an issue with the Windows installation. If you get errors extracting the RCP archive or running Papyrus-RT, consider installing in a directory closer to the root of your system!
The long-standing pathname issue when installing in deeply nested directories in Windows appears to still be an issue with the Windows installation. If you get errors extracting the RCP archive or running Papyrus-RT, consider installing in a directory closer to the root of your system!
And yes, of course, we are still painfully aware that there are still issues with the tool. A list of known issues is provided below, with workarounds, when available.
Note that the descriptions of the known issues, below, are summarized from their corresponding bug discussions.
Bugs are listed from most recent to oldest, with bugs found after the official release indicated with a leading "NEW" tag and those updated post-release indicated by an Updated tag.
- TBD
Back to Papyrus-RT v0.9 Release
Closed Bugs
There were 152 bugs closed as part of this release. That's too many to list here!
So I'll be lazy efficient and give you a link to the complete list of closed bug in Papyrus-RT 1.0.