[Pkg-shadow-devel] Work priorities

[Christian Perrier]

As we now have the supposedly last release for sarge behind us, we can
probably focus on other priorities.

What I currently see to be made is:

-check that the sarge branch is OK and contains what we have uploaded
 in the archive. Complete it if needed. This should be done by trying
 to build a package from it on one side....and trying to rebuild it
 from the archive on the other side...then compare.
 Volunteers?

-check that the sid branch currently builds a -32 version which is as
 close as possible as the -31sarge3 release
 The use of 00list allows for that even while adding more patches
 targeted to further versions
 The problem here is the difficulty we have to unapply the patches
 because of what we have  identified as a dpatch bug
 This makes rebuilding the package in a tree where it has already been
 built a real PITA, currently

Both these tasks need to have priority over other tasks such as bug
triage and resolution of pending problems.

We really need to have a -32 release in unstable as soon as possible
(my target is to upload it as soon as -31sarge3 enters testing). This
will allow us to have a strong work basis for the future work: The Big
Resync..:-)

Each bug we examine shows us that resyncing with upstream is to be
made as soon as possible because we currently lose a lot of time by
dealing with all those things we need to check both in the Debian
version and the upstream version. So, the earlier we resync shadow
with Tomasz official releases, the better it is.





--