-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Release Tracking of Test Flight #451
Comments
Dec 22 2016 0.1274 Issues included: #448 |
Dec 30 2016 0.1279 Issues included: #463 |
Dec 30 2016 0.1280 Issues included: #369 (delay issue) |
we need to updating this. it only takes 1 min |
3rd march 0.1295(0.1) : #532 |
6th march 0.1296(0.1) : #471 |
There are 31 items in the last push. Provide me a github #, description, date (give it to me in the sequence they were committed) |
Here are the requested details: |
Any logical reason why we were able to build Test Flight in the past with on average on 3 or 4 fixes before to now wait for a giant list of 31? Do we understand the word Test? |
21tst April 0.1305(0.11): #607 |
21st April 0.1306(0.11) : #598 |
26 April 0.1307(0.11) : #579 |
Thanks |
@sumairasaeed why we are not publishing the app on a regular basis? why we have not published for the last 11 days? |
Why are we posting after 2 weeks? |
29th May version 0.1319 (0.11) : #629 |
8th June version 0.1322 (0.11) : #633 |
14th June version 0.1323 (0.11) #625 |
@sumairasaeed
I am creating this task to track the release and what fixes have gone into the release.
So every time we do build we would create an entry here with build # and issues that got included in the build.
Example:
Data Build # Issues #
Dec 18 2016 Build 90 Issues included: #123, #390.....
The text was updated successfully, but these errors were encountered: