| [mdt-papyrus.dev] Planf for Luna and Kepler SRs |
|
Hi Dev-Team, as I was working more intensely with Kepler in the last days, I must admit that I still don’t think it has significantly improved with respect
to stability compared to the Indigo version. I did not use Juno at all, and I guess Papyrus still suffers from the huge refactoring that has been undertaken for Juno. In fact, often the entire connection between editor, ModelExplorer and Property sheet gets
broken. That happened never before in Indigo. I am still hoping that Luna or the following SRs of Kepler just care for stability and bugfixing instead of developing more and more almost finished features. What is the plan for the next version? Stabilizing, I hope so? Regards, Marc-Florian
Von: mdt-papyrus.dev-bounces@xxxxxxxxxxx [mailto:mdt-papyrus.dev-bounces@xxxxxxxxxxx]
Im Auftrag von Christian W. Damus Thanks, Camille. That's exactly what I needed to know. I agree that the API Tools will be a valuable aid post 1.0. Indeed, I think they're probable essential for a project of this size. :-) For my part, I'll spend some time reviewing the API in the CDO integration plug-ins and related stuff that I contributed to the main-line in Kepler. Please let me know if there's anything else that I can help with! cW On 2013-09-05, at 11:41 AM, LETAVERNIER Camille <Camille.LETAVERNIER@xxxxxx> wrote:
Hi Christian, As we don’t maintain a stable public API, we usually update all the plug-in versions at the same time. I’m supposed to do it this week for Luna
plug-ins (And it’s already been done for Kepler ones). We don’t have a planning for public APIs (And other Luna requirements) yet, but it is unlikely to happen before M4 or M5. Papyrus APIs have been moving a lot since the first version (Helios), and now there
is a lot of work to do to clearly define the APIs. So, until then, you can choose either 0.10.1 or 1.0.0. Everything will be updated to 1.0.0 really soon anyway. Features are updated at the same
time, with the same policy (i.e. all features/plug-ins have the same version number). This policy will change after 1.0.0. We’ll most likely rely on API tools and follow the standard Eclipse guidelines. Regards, __________________________ Camille Letavernier +33 (0)1 69 08 00 59 - camille.letavernier@xxxxxx CEA LIST - Laboratoire d'Ingénierie dirigée par les modèles pour les Systèmes Embarqués (LISE) Papyrus : http://www.eclipse.org/papyrus De : mdt-papyrus.dev-bounces@xxxxxxxxxxx
[mailto:mdt-papyrus.dev-bounces@xxxxxxxxxxx] De la part de Christian W. Damus
Currently, all of the Papyrus bundle manifests on the Git master branch declare plug-in version 0.10.1 (as on the maintenance branch). What is the team's policy for updating these versions? Do we make the appropriate update on first change to a plug-in project? Or, does somebody do a bulk update in the ramp-down of each milestone? (or release?) How about
the "trickle-up" to containing features? Luna intends to be release 1.0. I assume that means that all of the existing plug-ins will be updated to version 1.0. When will that happen? And until then, what should I do for
I actually have a new bundle ready to push for Papyrus Search in CDO repositories, so I need to know whether it should be version 0.10.1, 0.10.100, 0.11.0, or 1.0.0. And also what the concomitant update of the oep.extra.cdo
feature version should be. Last, on the subject of graduation to 1.0 ... One of the requirements of graduation is that the public API be stable. Currently, there are only a few Papyrus bundles that distinguish internal and external APIs; almost
none apart from the CDO plug-ins and a few core infrastructure plug-ins. What's the plan for API? Thanks! Christian _______________________________________________ |