I can answer that one. We recently wanted to try the latest mobile releases with Hawthorn. Unfortunately it was not possible because one of the mobile API used by the latest mobile release was changed post Hawthorn. We hope it will be included in Ironwood. See https://github.com/edx/edx-platform/commit/026d574576b8433817973d0a69a81b223471fa7a#diff-ad6006d4311d06b65d1bc3d6636ad9c9 for details.
Therefore, it is not possible for organizations using named releases to follow master or the latest releases for the mobile apps. Unless they cherry pick changes that are not in hawthorn.master for example. Maybe all we need is a page stating which mobile releases are working with which named releases? Is this more clear? On Tuesday, January 15, 2019 at 7:35:31 AM UTC-5, Ned Batchelder 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] <javascript:>> > 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] <javascript:>> 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/5459ac6f-2b7f-4036-8f49-d33ae970cd4b%40googlegroups.com.
