Hi Nick, no worries. I am actually documenting *and* scripting most of this (there are some manual steps) so that this process can be a shared thing and not just me :-) Well aware of that and working on it!
S. On Wed, May 20, 2015 at 12:29 PM, Nicholas Alexander <[email protected] > wrote: > Stefan, > > On Wed, May 20, 2015 at 8:39 AM, Stefan Arentz <[email protected]> > wrote: > >> Previously when we made a (beta/test) release we would just increment the >> Info.plist build numbers and tag master. This time for build #16 I have >> done it a bit differently: >> >> * We now have a build branch at >> https://github.com/mozilla/firefox-ios/tree/builds/AuroraV16 >> * The branch includes imported locales and also a snapshot of the l10n >> repository used >> * The branch includes a snapshot of our (Carthage) dependencies >> * The branch includes small last-minute tweaks that were needed (which >> need to move back to master) >> >> The end result is that we can now do a reproducible build, which is great >> when we want to map crash reports from Test Flight or App Store back to our >> code. >> > > This is a great process improvement! My intention is not to add to your > workload, but can I gently request either scripting this or adding the > step-by-step to the documentation? It would be nice to get at least one > other person to do this at least once. I'll volunteer to work with you > over IRC to do together for next weeks build. > > Huzzah for improvements \o/ > Nick >
_______________________________________________ mobile-firefox-dev mailing list [email protected] https://mail.mozilla.org/listinfo/mobile-firefox-dev
