Re: [mdt-papyrus.dev] increase for minor change

[Christian Damus <give.a.damus@xxxxxxxxx>]

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:

Hi

On 07/07/2016 16:26, Christian Damus wrote:

This is why other Eclipse projects cap their maintenance streams when the next release is published.  We should now do the same.

That certainly would solve the problem, but how do you plan to handle the very real customer pressure for updates? OCL has released 5.0.4 and 5.0.5 after 6.0.0 in order to satisfy Papyrus customers. This would have been difficult without the proactive +0.0.100.

    Regards

        Ed Willink

---

This email has been checked for viruses by Avast antivirus software. www.avast.com

_______________________________________________
mdt-papyrus.dev mailing list
mdt-papyrus.dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/mdt-papyrus.dev