Why can we not include both?

That's given the fact that rosapanel is already defaulting to adding both.

On 16 November 2013 16:25, Tomasz Paweł Gajc <[email protected]> wrote:
> So SW should be one and only launcher for finalrelease enabled by default.
>
> As we are not ready to have choice option while installing distro, then we
> can anly have simple decision made here.
> Wysłano z BlackBerry® w Orange
> ________________________________
> From: Raphaël Jadot <[email protected]>
> Sender: Raphaël Jadot <[email protected]>
> Date: Sat, 16 Nov 2013 22:20:01 +0100
> To: OpenMandriva Quality Assurance<[email protected]>; Tomasz Paweł
> Gajc<[email protected]>; OpenMandriva
> Workshop<[email protected]>; Cooker
> OpenMandriva<[email protected]>
> Subject: Re: [om-qa] Things must be done to have final release
>
> About point 4 I'd like to stress the fact SW _was_ winner (and ko not a
> winner) with two times more for votes for simple welcome than kickoff). Only
> by adding a previous survey where joao asked broadly (ie not only to om
> users) what people use, it brought kickoff closer, but even with this
> previous survey, sw is still winner. If we respect our survey and users, we
> have two solution, or we have sw alone, or we have sw along with ko. But we
> have to include sw.
>
> (note i'm not a defender of sw, i prefer homerun or appmenu-qml, but we
> can't make a survey, have a winner and choose another)
>
>
> "Tomasz Paweł Gajc" <[email protected]> a écrit :
>>
>>
>> A release of final product is on 2013-11-22 and most of us will be
>> unavailable
>> on that day. So  to have things go smooth i've prepared a plan and MUST
>> TODO -
>> will move this to a https://wiki.openmandriva.org/en/2013.0_release_plan
>> with
>> nice frames. For each action there must be at least one preson who can
>> take
>> task for 100% without excuses etc, so please rise your hands by sending an
>> e-
>> mail to me or directly edit wiki page.
>>
>> Before ISO build:
>>
>> 1. Documentation on wiki (as folowed by Robert Xu e-mail)
>>
>> a) Overview: https://wiki.openmandriva.org/en/2013.0
>> b) What's New: https://wiki.openmandriva.org/en/2013.0/New
>> c) Release Notes: https://wiki.openmandriva.org/en/2013.0/Release_Notes
>> d) Screenshots
>> e) Feature highlights
>>
>> 2. Update distro-release package
>>
>> a) release-notex.html and release-notes.txt - based on point 1.c
>> b) CREDITS - highly outdated (mdv 2010) - we needs list on contributors,
>> testers and translators - well i've did it but please reviev and add if
>> someone is missing
>>
>>
>> https://abf.rosalinux.ru/openmandriva/distro-release/blob/openmandriva2013.0/CREDITS
>>
>> c) What should be final distaname ? Currently it is:
>> %define distname RC2 (Oxygen)
>>
>>
>> 3. This needs attention
>> https://issues.openmandriva.org/show_bug.cgi?id=198
>>  if no response till tuesday i'll clean this out
>>
>> 4. Only one
>> launcher should stay - winner was kickoff - rosapanel package
>>
>> needs and update.
>>
>> ISO build
>>
>> 1. Bero please build ISO on tuesday 2013-11-19 after we will have above
>> thing
>> cleared
>>
>> Q&A
>>
>> 1. ISOs needs testing - nothing should change much but nobody knows :)
>> 2. GnG decision on Thursday 2013-11-21
>>
>> Mirroring
>>
>> 1. Push ISOS after Q&A GO on ibiblio and sf.net on Thursday 2013-11-21
>>
>> Announcement
>>
>> 1. Let's work together on announcement - should be done on google docs ?
>> 2. If it is possible push announcement with nice screenshots on blog,
>> social
>> medias and others like phoronix, distrowatch on Friday 2013-11-22 (it can
>> be
>> even just past thursday midnight 00:01 :p)
>>
>> Release Party in Prague
>> 1. Well if everything will go smooth then we will have a release beer in
>> Prague at 2013-11-22 evening
>>
>> If someone finds anything
>> more please respond here.
>>
>> TPG
>>
>> ________________________________
>>
>> OM-QA mailing list
>> [email protected]
>> http://ml.openmandriva.org/listinfo.cgi/om-qa-openmandriva.org
>
>
> --
> Best regards, meilleures salutations
> (K9-Mail Android)
> Raphaël Jadot
>
>
>



-- 
Robert Xu :: protocol.by/rxu

Reply via email to