On Thu, 2007-09-20 at 18:43 -0500, Douglas McClendon wrote:
Rahul Sundaram wrote:
> Douglas McClendon wrote:
>> How about we split livecd-iso-to-disk into its own package,
>> specifically because of the use-case scenario of a user just wanting
>> to put their newly downloaded f8-livecd on usb, without any need or
>> interest in full-blown livecd-creation?
>>
>> And install it by default, perhaps even in the minimal base spin config?
>
> This sounds like a good idea especially if we provide a menu option to
> make this feature more visible to users and reviewers who don't read the
> release notes which is unfortunately quite a lot.
I could throw together a ghetto zenity gui pretty quickly. The only
user interaction is
[snip]
I'm curious, what kind of deadlines should I be thinking about
for this
and other livecd related things.
Technically speaking, features should mostly be done prior to the
feature freeze (test2). How much of a feature this is could be
arguable, though.
I.e. the f8 devel freeze is Oct 4th, as of f8t3 release. But then
there
is an f8t3 devel freeze as of Sept 25th (along with translation freeze).
What sort of development is considered acceptable between those two dates?
Bugfixes only. The big difference is the severity of bugs fixed changes
as of Oct 4th.
Obviously I would like to get anything in by say... tonight, so that
Jeremy has time to decide to accept it and commit it before tuesday,
and then not try to get anything in after that.
And would this theoretical gui livecd-iso-to-disk separate package fall
outside the scope of even the oct-4th devel freeze, because it is a
'new' package?
If we don't install it by default, then it would be reasonable to put
in. So given that livecd-tools isn't installed by default anywhere, in
that respect, we could just put it in. But Rahul I think wants it
installed by default.
That said, in any case, I'm willing to put it on a branch for now
Jeremy