Problems revealed by a report of detailed changes to 8.2.1 tickets.
C. Scott Ananian
cscott at laptop.org
Mon Dec 22 16:12:44 EST 2008
On Mon, Dec 22, 2008 at 1:57 PM, Ed McNierney <edmcnierney at gmail.com> wrote:
> Are we able to promptly and regularly generate 8.2.1 builds that
> reflect the work being done?
Yes. All completed work should be packaged and put in
public_rpms/staging for testing, with an appropriate changelog.
Staging builds are automatically generated (every three hours) if/when
new packages are added.
Most "fixed bugs" are not yet included in the staging builds. I've
gone through most bugs in
http://dev.laptop.org/report/38
and either packaged/added them to staging myself, or pinged the bug
owner to do so. Once we get everything included and tested in a
staging build, we can make "release candidate quality" builds easily
from the contents of the staging repository. That process mostly
involves testing strategy: do we want to wait until all the bugs are
fixed to make an RC build, or try to generate a series of RC builds
which fix only one thing at a time, or something else. I'm lazy, I'd
prefer the first option.
--scott
--
( http://cscott.net/ )
More information about the Devel
mailing list