Hi all,
Main topic in CLT call this week was backports with a few Quincy updates
- Backports
- Backport team is now only 1 person
- Devs need to mostly handle backports themselves
- Need new statuses in redmine for "needs testing". Right now trackers sit in "In Progress" when devs create backport and there's no differentiation for when dev work is done and testing can begin.
- Having trackers marked "Resolved" when changes get into the branch can confuse users who care more about which stable release the fix got into. Might be better for them to sit in pending release until the fix lands in an actual release.
- Talks about whether or not automation for this is necessary
- Backport script is fairly quick
- Considering a unified effort to clear out queue of PRs needing backport. To be discussed later.
- Possible automation for moving trackers from pending release to resolved as part of the stable release process.
- Master tickets should probably stay in pending backport until all backports set to pending release then they can be marked resolved
- Quincy
- In good shape, a couple things left in backport queue, no blockers
- Hoping to get rc out this week
- Teams to update slides on Quincy for board meeting next week
- Testing Suites
- Currently looking good, most suites have < 10 failures
- Application for GSoC submitted, waiting on acceptance
- Some discussion of shirt design for Quincy release
_______________________________________________ Dev mailing list -- dev@xxxxxxx To unsubscribe send an email to dev-leave@xxxxxxx
