On 10/14/2013 08:55 PM, "Jóhann B. Guðmundsson" wrote:
On 10/14/2013 06:52 PM, David Cantrell wrote:
If you want the installer to run on the OS it is installing,
development of
the installer has to be after everything else completes
Interesting never thought of it like that but this actually might work
at the cost of the marketing or atleast potentially uninstallable
lives which have been of questionable benefit to us in QA anyway (
produces a lot of dupes which might already be fixed ) .
How much time would you guys need if we moved the entire installer
testing until after "final" would a sprint of a month with dedicated
QA resources suffice?
Or we keep the core/baseOS bits on separate release cycle ( aligned with
the kernel ) and Anaconda on a finalize cycle ( month ) after it ( new
release every 4ish months, 3 releases per year )?
JBG
_______________________________________________
Anaconda-devel-list mailing list
Anaconda-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/anaconda-devel-list
