Hi, Simon,
I can try to update the builds, but I shall have to see whether I quite understand how the target platform selection works. I expect to plead with Céline for help. 😉
There is only one maintenance stream for Neon, so any fixes needed in Neon now will be targeting Neon.2 in December. Eclipse doesn’t have maintenance on maintenance, but there is the notion of a “patch feature” that can slice and dice a p2 profile in weird ways that probably make further updates difficult or risky. I’ve heard of these being employed in very special cases and only ever in commercial shrink-wrapped products and I’ve heard opinions that they are best avoided. I know next to nothing about how they work.
For myself, I’ve managed to punt quite a few of my 0.8 bugs into 0.9 because they’re blocked on fixes needed in UML2 or Papyrus, which of course are now past Neon.1. So, whether they gated 0.8 is somewhat moot, I suppose. It seems that most of the bugs I’ve picked ended up this way. Anyways, now that Papyrus is open for Neon.2 business, some of those patches could now be merged, but I suppose it will be better to let them hang in suspended animation and take the next 0.8 bug on the list? And hope it doesn’t also require fixes in Papyrus … After seeing to the builds, of course.
On 28 September, 2016 at 13:18:30, Simon Redding (sredding@xxxxxxxxxxxxx) wrote: Christian, Yes, we should move to build against neon.1. Can you make that change? I also have a question about maintenance fixes. If we find problems in Papyrus that need to be fixed, can they be back ported into neon.1, or is there some other maintenance branch against which we need to build? If this is the case, then I assume we need to specifically identify fixes which need to get back ported? As for the 0.8 release, we still have 20 open issues in the backlog or assigned. All these bugs right now are viewed as gating, and no one should work on bugs which are not on this list. New bugs are triaged by Charles, so this is basically how we control what gets submitted. Given where we are, I am thinking that a realistic target for 0.8 is going to be mid-October, but we should review on the Friday sync call. I will propose a more detailed release timeline before the meeting. Regards, Simon What is the plan for finishing the 0.8 release? Now that Papyrus Neon.1 is final and Papyrus is starting to build nightlies for Neon.2, I expect that we need to update our builds (and the tester setup) to take the Papyrus Neon.1 release and not those nightlies, right? And do we have a target date for the 0.8 release? Is there a particular ramp-down policy with respect to bug triage and review/submission of changes in the final days of the release? _______________________________________________
papyrus-rt-dev mailing list
papyrus-rt-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/papyrus-rt-dev
|
