Revision history [back]

Hey; given the recent QA team limitations it feels tempting to propose a "Jolla greenlight" - á la Steam Greenlight, for instance. Where Apps are uploaded in BETA stage; simple RPM validation pass is only entrance requirement pass and app is then distributed as BETA to users.

Pros : users can beta-test apps in a crowd-sourced way Cons : needs tools to provide developers with feedback

Hey; given the recent QA team limitations it feels tempting to propose a "Jolla greenlight" - á la Steam Greenlight, for instance. instance.

Where Apps are uploaded in BETA stage; simple RPM validation pass is only entrance requirement pass and app is then distributed as BETA to users.

Hey; given the recent QA team limitations it feels tempting to propose a "Jolla greenlight" - á la Steam Greenlight, for instance.instance;

Where where SFOS Apps are uploaded in BETA stage; simple RPM validation pass is only entrance requirement pass and app is then distributed as BETA to users.users. Actual harbour QA would then "just" have to validate the app once Greenlight is done.

• Pros : users can beta-test apps in a a crowd-sourced way

• Cons : needs tools to provide developers with feedbackfeedback and differentiate Greenlighted beta apps from QA-passed ones.

Hey; given the recent QA team limitations it feels tempting to propose a "Jolla greenlight" - á la Steam Greenlight, for instance;

where SFOS Apps are uploaded in BETA stage; simple RPM validation pass is only entrance requirement pass and app is then distributed labeled as BETA to users. Actual harbour QA would then "just" have to validate the app once Once Greenlight is done.OK (=all bugs closed), app can be submitted to harbour QA. Could make things easier?

• Pros : users can beta-test apps in a crowd-sourced way

• Cons : needs tools to provide developers with feedback and differentiate Greenlighted beta apps from QA-passed ones.

Hey; given the recent QA team limitations it feels tempting to propose a "Jolla greenlight" - á la Steam Greenlight, for instance;

where SFOS Apps are uploaded in BETA stage; simple RPM validation pass is only entrance requirement pass and app is then distributed labeled as BETA to users. Once Greenlight is OK (=all bugs closed), app can be submitted to harbour QA. Could make things easier?

• Pros : users can beta-test apps in a crowd-sourced way

• Cons : needs tools to provide developers with feedback and differentiate Greenlighted beta apps from QA-passed ones.

Hey; given the recent QA team limitations it feels tempting to propose a "Jolla greenlight" - á la Steam Greenlight, for instance;

where SFOS Apps are uploaded in BETA stage; simple RPM validation pass is only entrance requirement and app is then distributed labeled (labeled as BETA BETA) to users. Once Greenlight is OK (=all bugs closed), app can be submitted to harbour QA. Could make things easier?

• Pros : users can beta-test apps in a crowd-sourced way

• Cons : needs tools to provide developers with feedback and differentiate Greenlighted beta apps from QA-passed ones.

Hey; given the recent QA team limitations it feels tempting to propose a "Jolla greenlight" - á la Steam Greenlight, for instance;

where SFOS Apps are uploaded in BETA stage; simple RPM validation pass is only entrance requirement and app is then distributed (labeled as BETA) to users. Once Greenlight is OK (=all bugs closed), app can be submitted to harbour QA. Could make things easier?

• Pros : users can beta-test apps in a crowd-sourced way

• Cons : needs tools to provide developers with feedback and differentiate Greenlighted beta apps from QA-passed ones.