| Re: [mdt-papyrus.dev] increase for minor change |
|
This is also the topic discussed on the components area for Papyrus. It would be really useful for them to have more frequent releases, especially from the core
Papyrus. As for example, Papyrus-RT currently targets the Neon.1, as it needs some updates on the core Papyrus.
The “issue” with that is to ensure a quality level / robustness and very clear API management (not only java for example, but also configuration models, etc.).
That means that for subprojects as Papyrus-xtUML and Papyrus-RT, we must ensure that the customizations are stable enough to let them adopt new features, while still having a comfortable level of performances / robustness, and without requiring too much migration
efforts. It is quite OK to be fast evolving when we are a leaf component, with no more projects depending on you. This is a bit harder when the project is reused by several sub-projects. Regards, Rémi ------------------------------------------------------- Rémi SCHNEKENBURGER +33 (0)1 69 08 48 48 CEA Saclay Nano-INNOV Institut CARNOT CEA LIST De : mdt-papyrus.dev-bounces@xxxxxxxxxxx [mailto:mdt-papyrus.dev-bounces@xxxxxxxxxxx]
De la part de Christian Damus Projects such as CDT are planning now to make more frequent (even quarterly!) feature releases, so that the maintenance streams are hardly relevant any more. That appeals
to me. And this was a major driver in the Simultaneous Release train’s move to four quarterly follow-up releases that are no longer couched as “maintenance” releases but may contain new feature content and even new projects. Papyrus is such a quickly-evolving creature that I think we should seriously consider making quarterly feature releases and re-thinking the maintenance program. cW On 7 July, 2016 at 11:00:04, Ed Willink (ed@xxxxxxxxxxxxx) wrote:
|
