Fwd: Mentoring for a new member from Brazil.
Robie Basak
robie.basak at canonical.com
Tue May 21 08:31:11 UTC 2013
On Sat, May 18, 2013 at 12:37:04AM -0300, Tiago Porangaba wrote:
> However I am not sure what you mean saying *"isolating and*
> *cherry-picking fixes shouldn't be too difficult."*
> *
> *
> My guess is that you mean that I should pick a triaged bug, pick one fix
> from some suggested fixes and submit this fix (after QA). Is that right?
The SRU process requires that we fix the development version first. This
is often achieved by taking the latest upstream version that might
already have the problem fixed, or applying our own fix.
Then we have to backport the fix to stable releases for bugs where we
feel it is appropriate. You can find a list of such bugs at [1] that
have been nominated for (Precise) 12.04, for example. To prepare the
fix, I'm proposing that as a programmer you may be able to more easily
locate the patch that fixed the problem in the development version,
backport it (change it as needed so that it applies correctly to the
older version and still fixes the problem), make it minimal if necessary
(so that it's easier to understand and minimises the chances of
regressions), test it, and prepare a debdiff for an update to the stable
release.
Does that make sense?
Robie
More information about the ubuntu-server
mailing list