| Re: [papyrus-rt-dev] 0.8 Release Ramp Down |
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 From: papyrus-rt-dev-bounces@xxxxxxxxxxx [mailto:papyrus-rt-dev-bounces@xxxxxxxxxxx] On Behalf Of Christian Damus Hi, Team, 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? Thanks, Christian |