| [mdt-papyrus.dev] Papyrus Plug-in Version Management |
Hi, Team, 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 |