I took FC15's SRPM as base and started patching it to bring pino into proper shape. It builds with current FC15's builddeps already (patches in Fedora's bug tracker) and maximizes properly. I want to build autorefreshing into it and fill menus this or next week.
Does it make sense to provide the patches to Fedora and propose them to upstream later or should I develop against the upstream's default branch and ask upstream to reintegrate them in hope that the changes will flow into Fedora later?
Cheers,
-- Dmitri Bachtin
2011/4/8 Alex Hudson <fedora@xxxxxxxxxxxxxx>
Adam,
Sorry, I think you're misunderstanding what I'm asking, so let me
On Fri, 2011-04-08 at 08:58 -0700, Adam Williamson wrote:
> On Fri, 2011-04-08 at 08:58 +0100, Alex Hudson wrote:
> > I apologise for bringing this up so late in the beta cycle - I'm sure
> > the beta is spinning as I type - but I honestly don't think it can ship
> > in this state.
>
> As far as that goes - the functionality of non-vital apps within the
> image is not an issue for the Beta criteria. Unless it's on the panel by
> default and crashes (which it isn't), nothing to do with pino can block
> the Beta.
clarify: I'm not asking that this block the beta, I'm asking whether or
not this should be shipped by default.
I mentioned the beta because ideally stuff like this would be sorted out
by now. I should have just said "so late in the release cycle".
I think shipping F15 with Pino included on the Live CD by default, in
the condition it is currently in, would be a huge error.
Cheers,
Alex.
--
This message was scanned by Better Hosted and is believed to be clean.
http://www.betterhosted.com
--
-- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel
