Survey LTR usage

[anitagraser]

Deadline

2020-03-31

Notes

https://lists.osgeo.org/pipermail/qgis-psc/2020-March/008290.html

Question proposals included below (quoted from an earlier proposal also in this thread).

• Which QGIS version are you currently using (3.4, 3.10, another LR)
• How often do you upgrade patch versions (monthly, sometimes, never)
• When do you plan to upgrade to the next version
• Size of organisation / installations (1-2 user, 3-10 users, 11-100 users, > 100 users)
• What is the main reason for not upgrading patch releases more often (Why should I if everyting just works; Internal testing takes too long; Internal application deployment is complicated/expensive; I already update every patch release; Patch releases tend to break things; I didn't know there are patch releases; Other)
• What is the main reason for not upgrading the main QGIS version earlier (Internal testing takes time; Never change a running system - I do not trust new releases; Plugins are incompatible; I always wait for x patch releases before upgrading out of habit; Other)
• In an ideal world, how often would you prefer to have new LTR versions (1y, 2y, 5y, I use every release regardless if LTR or not)
• Do you have a support agreement with a core developer / company to fix blocker issues before upgrading

[andreasneumann]

I would add the following question:

• how many dot releases do you wait until you install a new LTR version?

As an example in our organization we wait for at least 3-4 dot releases until we dare to roll it out to our users

That doesn't mean that some power users aren't testing the earlier versions, or even before the release.

[haubourg]

I would also ask what distribution system they use. So that we know if OSGEO4W is 99.9% of the corporate user's. That would really help in focusing packaging efforts and harden our OSGEO4W policy.

[jef-n]

I would also ask what distribution system they use. So that we know if OSGEO4W is 99.9% of the corporate user's. That would really help in focusing packaging efforts and harden our OSGEO4W policy.

You mean Windows? The standalones use the same binaries.

[anitagraser]

• If you use Windows: Which installer do you use? (stand-alone or OSGeo4W)
• Do you still need 32bit installers?

[timlinux]

Nothing to add from me

[anitagraser]

Collected and sorted questions

1. Which QGIS version are you currently using (3.4 LTR, 3.10 LTR, 3.12, another release, development version)
2. Which is the next version you plan to upgrade to? (3.10 LTR, 3.12, dev)
3. How often do you upgrade patch versions, (e.g. from 3.10.0 to 3.10.1) (monthly, sometimes, never)
4. If you use LTR: when do you plan to upgrade to 3.10 LTR? (already upgraded, April 2020, Mai 2020, June 2020, July 2020, later)?
5. If you use LTR: how many dot releases do you wait until you install a new LTR version (0, 1, 2, >2)
6. Size of organisation / installations (1-2 user, 3-10 users, 11-100 users, > 100 users)
7. If you use Windows: Which installer do you use? (stand-alone or OSGeo4W)
8. Do you still need 32bit installers?
9. What is the main reason for not upgrading patch releases more often (Why should I if everything just works; Internal testing takes too long; Internal application deployment is complicated/expensive; I already update every patch release; Patch releases tend to break things; I didn't know there are patch releases; Other)
10. What is the main reason for not upgrading the main QGIS version earlier (Internal testing takes time; Never change a running system - I do not trust new releases; Plugins are incompatible; I always wait for x patch releases before upgrading out of habit; Other)
11. In an ideal world, how often would you prefer to have new LTR versions (1y, 2y, 5y, I use every release regardless if LTR or not)
12. Do you have a support agreement with a core developer / company to fix blocker issues before upgrading

TODOs

• Clarify options for answers
• Insert questions into Kobo
• Call for translations

[anitagraser]

@m-kuhn Regarding the question "When do you plan to upgrade to the next version?": would you like respondents to provide a date or some relative time with respect to the next release (3.14)?

[m-kuhn]

The main interest for this question was orgs who currently use 3.4 and plan to upgrade to LTR 3.10. Is it possible to offer months (2020/04, 2020/05, ...)?

[anitagraser]

Is it possible to offer months (2020/04, 2020/05, ...)?

Yes, I think so.

[m-kuhn]

Should we add something along the lines "which version is the next you are upgrading to" to separate users that stick to LTR and those that stick to LR?

[anitagraser]

In 2018, we asked users how often they upgrade http://blog.qgis.org/2018/12/03/user-question-of-the-month-dec-18-answers-from-nov/. I guess we can do that again.

[m-kuhn]

Thanks @anitagraser, I also think so.
What we will have with thi survey is the possibility to do statistics over different variables (e.g. regression analysis on size of organization vs. update interval)
From my side it looks good now. Let me know if you need something else.

[anitagraser]

I've set up the questions on Kobo. This link should provide read access to anyone with an account: https://kf.kobotoolbox.org/#/forms/a8Fxqyxh4HyNHNng7ADSez

@m-kuhn It would be great if you could check that everything is as expected before I send out the call for translations.

I've also invited everyone who previously volunteered to translate questions of the month and given them the necessary edit right.

[m-kuhn]

Thanks @anitagraser

Some thoughts:

• 1: Should we replace "Another release" with "Another 2.x" and "Another 3.x"?
• 2: Add "not planned, other"
• 3: "Never" -> "Less than each half year" -> "Sometimes" -> "More than each half year"
• All radio button: Add "Does not apply" (for people that don't know about 32 bit, or those that don't use LTR)
• For people who use more than one release in parallel, clarify that they should reply for the version which is most widely used in their org

[anitagraser]

@m-kuhn I'd like to give you edit rights. Please send me your Kobo account name so I can add you

[m-kuhn]

It's mkuhn

[anitagraser]

Thanks! Note that none of the questions is mandatory. It should be possible to submit without filling them. But we can add explicit "Does not apply" options if you prefer.

[m-kuhn]

I think it would be better, the expectation for radio buttons is that they stay checked (even if checked accidentally).

[mbernasocchi]

Thanks a lot @anitagraser! I looked in kobo and it looks nice. if you need help I'm mbernasocchi there.

to me, we should add 2.18 to Which QGIS version are you currently using.

[m-kuhn]

@anitagraser questions updated, how do they look to you?

[anitagraser]

@mbernasocchi I've added you

[mbernasocchi]

looks great thanks, I just did a mini fix:
Question 2 from More often to More often, as soon as they appear

[m-kuhn]

looks great thanks, I just did a mini fix:
Question 2 from More often to More often, as soon as they appear

Actually, we don't ship patch releases more often, what's the meaning of this ?

I.e. can we remove this option or merge it with monthly?

[mbernasocchi]

I.e. can we remove this option or merge it with monthly?
done: Monthly, as soon as they appear

[m-kuhn]

Thanks.
Ready for sending to translation?
Let me know if I can still help.

[anitagraser]

I'll send out the call for translations now. Thank you for your help!

[anitagraser]

Results of the survey have been sent out on the mailing list and posted on the blog http://blog.qgis.org/2020/04/02/ltr-usage-survey/

You can find the raw survey responses here:
https://drive.google.com/open?id=1lECEhusQcpDpb50MSMYP_5BDfEl4jXeV