Oh, and one other thing: Why not tag the apps, and then let people decide for themselves if they want to use a tagged open-edx release, or if they want to use master?
--Ned. On Wed, Jan 16, 2019 at 11:57 AM Ned Batchelder <[email protected]> wrote: > J'aime, thanks for your perspective. I'm still trying to understand: does > the master of the mobile apps work against Hawthorn? You say they work > against Ginkgo, so how could they be broken against Hawthorn? You > mentioned cherry-picking, is that picking changes to the mobile app, or to > the server? > > --Ned. > > On Wed, Jan 16, 2019 at 1:41 AM J'aime Ohm <[email protected]> wrote: > >> I agree with Lupus and Ned that it is best to stay on latest for mobile. >> Changes to the API are generally minor or nonexistent between versions and >> are easy to cherrypick. I'm running master against a Ficus and a Ginkgo >> instance and will be running against a Hawthorne instance when it's ready >> for me in the next couple of months. My situation is similar to Pierre's, >> except I'm running master against even older backend(s). >> >> I agree with Pierre, the cherrypicking is annoying. I've found the >> changes are minor though, for avoiding a change. To avoid having people >> cherrypick, the mobile team might consider keeping small API changes behind >> feature flags for a platform release or two. >> >> Some reasons to stay on master include... >> - older versions of an app often don't run as-is, even if the version of >> Xcode, OS, Swift, and Android Studio are named, because of changes by Apple >> that affect this and are uncontrollable >> - it's more natural to contribute PRs if you're testing and running >> against master >> - like Lupus says, security updates >> - other maintenance updates that may be time sensitive, like support for >> new devices or new operating systems or new requirements by the stores >> >> >> >> On Tuesday, January 15, 2019 at 1:14:15 PM UTC-8, Lupus Furyo wrote: >>> >>> Hi Ned, >>> I was replying from my gmail inbox, I did not see Pierre's last reply >>> regarding usability. My remark was of general type, especially concerning >>> Sec of an App. Mobile apps get updated too often due to known concerns. >>> Perhaps, this is why Marco does not like tagging Open edX App with >>> named.releases. Anyways, please ignore my remark regarding this matter. >>> Pierre has already elaborated his question and suggestion thoroughly. >>> >>> Best, L. >>> >>> >>> On Wed, Jan 16, 2019 at 12:30 AM Ned Batchelder <[email protected]> wrote: >>> >>>> Lupus, can you explain why that is? Did you see Pierre's experience >>>> that the latest mobile app didn't work with Hawthorn? >>>> >>>> Thanks, >>>> >>>> --Ned. >>>> >>>> On Tue, Jan 15, 2019 at 11:48 AM Lupus Furyo <[email protected]> >>>> wrote: >>>> >>>>> In case of mobile clients, generally, it is always better to stick to >>>>> master. This does not concern Open edX only. >>>>> >>>>> On Tue, Jan 15, 2019 at 4:35 PM Ned Batchelder <[email protected]> wrote: >>>>> >>>>>> Robert, >>>>>> >>>>>> I asked Marco Morales about this, and he said, "I'm not convinced it >>>>>> is all that helpful to pin or tag these specifically? We publicize named >>>>>> platform release dates, mobile release version dates (with github tags). >>>>>> I'd rather people stay closer to master for mobile (which they generally >>>>>> do) rather than tracking all breaking changes across the two." >>>>>> >>>>>> What do you think of that? >>>>>> >>>>>> --Ned. >>>>>> >>>>>> On Thu, Jan 10, 2019 at 2:34 PM Ned Batchelder <[email protected]> wrote: >>>>>> >>>>>>> Robert, >>>>>>> >>>>>>> I believe we will be tagging them for Ironwood, yes. >>>>>>> >>>>>>> --Ned. >>>>>>> >>>>>>> On Wed, Jan 9, 2019 at 11:55 AM Robert Gérin-Lajoie < >>>>>>> [email protected]> wrote: >>>>>>> >>>>>>>> Hi Ned, will you tag the mobile apps (iOS and Android) with >>>>>>>> Ironwood? >>>>>>>> >>>>>>>> Robert >>>>>>>> >>>>>>>> Le mardi 8 janvier 2019 15:52:52 UTC-5, Ned Batchelder a écrit : >>>>>>>>> >>>>>>>>> Hey everyone, >>>>>>>>> >>>>>>>>> The next release of the Open edX software is "Ironwood." We are >>>>>>>>> getting ready to start the release process. The first step is >>>>>>>>> creating the >>>>>>>>> open-release/ironwood.master branches in the appropriate repos. I >>>>>>>>> plan to >>>>>>>>> do this on Friday, January 18th. >>>>>>>>> >>>>>>>>> Anything merged by that date will be part of Ironwood; anything >>>>>>>>> merged after that date will have to wait for the next release. >>>>>>>>> >>>>>>>>> A week or two after the branches are created, we will have a beta >>>>>>>>> for everyone to test. Then after a few weeks of community testing, >>>>>>>>> Ironwood will be officially released. >>>>>>>>> >>>>>>>>> If you have any questions or concerns, respond to this thread, or >>>>>>>>> send an email to [email protected]. >>>>>>>>> >>>>>>>>> Thanks, >>>>>>>>> >>>>>>>>> --Ned. >>>>>>>>> >>>>>>>> -- >>>>>>>> You received this message because you are subscribed to the Google >>>>>>>> Groups "General Open edX discussion" group. >>>>>>>> To view this discussion on the web visit >>>>>>>> https://groups.google.com/d/msgid/edx-code/76a8f4e8-5a7e-4683-8b6c-75c76f4eeb00%40googlegroups.com >>>>>>>> <https://groups.google.com/d/msgid/edx-code/76a8f4e8-5a7e-4683-8b6c-75c76f4eeb00%40googlegroups.com?utm_medium=email&utm_source=footer> >>>>>>>> . >>>>>>>> >>>>>>> -- >>>>>> You received this message because you are subscribed to the Google >>>>>> Groups "General Open edX discussion" group. >>>>>> To view this discussion on the web visit >>>>>> https://groups.google.com/d/msgid/edx-code/CAGtJPNPsxeXas_WKonGVpMAmpZQMevTRYffbzroT%3DAeSo57PhQ%40mail.gmail.com >>>>>> <https://groups.google.com/d/msgid/edx-code/CAGtJPNPsxeXas_WKonGVpMAmpZQMevTRYffbzroT%3DAeSo57PhQ%40mail.gmail.com?utm_medium=email&utm_source=footer> >>>>>> . >>>>>> >>>>> -- >>>>> You received this message because you are subscribed to the Google >>>>> Groups "General Open edX discussion" group. >>>>> To view this discussion on the web visit >>>>> https://groups.google.com/d/msgid/edx-code/CA%2BaB0d-rmF%3D%3DUtB3yF3J9Urw4ugRPizYu6v69099tCXneh40jA%40mail.gmail.com >>>>> <https://groups.google.com/d/msgid/edx-code/CA%2BaB0d-rmF%3D%3DUtB3yF3J9Urw4ugRPizYu6v69099tCXneh40jA%40mail.gmail.com?utm_medium=email&utm_source=footer> >>>>> . >>>>> >>>> -- >>>> You received this message because you are subscribed to the Google >>>> Groups "General Open edX discussion" group. >>>> To view this discussion on the web visit >>>> https://groups.google.com/d/msgid/edx-code/CAGtJPNNC%2BTZnode7aQz6h%2BDHh%3D48dWg%3Dy4RrGna9ERY8FRXN5g%40mail.gmail.com >>>> <https://groups.google.com/d/msgid/edx-code/CAGtJPNNC%2BTZnode7aQz6h%2BDHh%3D48dWg%3Dy4RrGna9ERY8FRXN5g%40mail.gmail.com?utm_medium=email&utm_source=footer> >>>> . >>>> >>> -- >> You received this message because you are subscribed to the Google Groups >> "General Open edX discussion" group. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/edx-code/243bf16d-d148-46b0-a316-d6561e51594d%40googlegroups.com >> <https://groups.google.com/d/msgid/edx-code/243bf16d-d148-46b0-a316-d6561e51594d%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> > -- You received this message because you are subscribed to the Google Groups "General Open edX discussion" group. To view this discussion on the web visit https://groups.google.com/d/msgid/edx-code/CAGtJPNMN0LPA7dP30po_heC11y6Wn%2BcFCVKFHFEAcsU-s8jZkg%40mail.gmail.com.
