Could you clean up all the attached patch and branches to leave only the
ones relevant to the sru?
All updates should be targeted to {intrepid,jaunty}-proposed instead of
{intrepid,jaunty} since the latter are closed.
Each changelog entry should refer to this bug number so that SRU team
can easily find this bug when they're reviewing the new package in the
NEW queue.
The jaunty,intrepid sru changelog (and branches) should be based on the
intrepid/jaunty changelog. There shouldn't be any mention of karmic in
there. It should only document the changes between the existing version
in intrepid/jaunty and the new one.
To make it easier for reviewing the diff, I'd suggest to attach a
debdiff of the landscape-client SRU. Another solution is to branch the
landscape-client package branch (at lp:ubuntu/jaunty/landscape-client
and lp:ubuntu/intrepid/landscape-client) and import the new upstream
tarball (using bzr merge-upstream from the bzr-builddeb plugin). Prepare
and push the new branch and submit a merge proposal for the
ubuntu/{jaunty,intrepid}/landscape-client branch and attach it to this
bug. That way the diff can be easily seen and reviewed.
--
update intrepid and jaunty to landscape-client 1.3.2.3
https://bugs.launchpad.net/bugs/347983
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
