Hi,
I would like to know why f-droid is quite slow (3 months) about updating telegram-FOSS even if the source code is released by telegram team in 1 weeks and telegram-FOSS updates it in few weeks.
Thank you
I’m not sure what you mean. The last tg-foss version was released 2 weeks ago on fdroid (5.6.1)
I mean that f-droid takes a long time before to upgrade the package.
For instance:
- Telegram official released 5.7.1 source code on 4th June
- Telegram FOSS released 5.7.1 on 8th June
- Telegram FOSS f-droid released 5.4.0 on 17th March (released by Telegram official on 3rd March)
5.6.1 is available since May 25
5.7.1 was build June 9 and awaits publishing
Always use the F-Droid client to get info on new apps and timely notifications on app updates. The website is updated a little slower (work in progress).
Well, if the Web site is not up to date…Why did you write this on the description page?
‘’‘Warning:’‘’ While this build is based on a pure-floss fork, original upstream is not always fast with publishing the source code for recent versions.
This is clearly not true.
Ok so they pushed the source faster this one time and this should wash all the previous years actions?
Mar 30, 2017 Update to 3.18.0
4 months
Jul 8, 2017 Update to 4.1.1
5 months
Dec 8, 2017 Update to 4.6.0
7 months
Jul 30, 2018 Update to 4.9.0
1 month
Aug 27, 2018 Update to 4.9.1
5 months
Jan 23, 2019 Update to 5.2.1
Feb 8, 2019 Update to 5.3.1
Mar 3, 2019 Update to 5.4.0
2 months
May 14, 2019 Update to 5.6.1
…yeah, I’m glad they push faster NOW…this doesn’t make that text false.
1 Like
Of course, this is the reason for which now the sentence is not true.
| Version | binary | source code | delay |
|---|---|---|---|
| 3.18.0 | 03/04/17 | 31/03/17 | -3 |
| 4.1.1 | 24/07/17 | 08/07/17 | -16 |
| 4.2.1 | 28/07/17 | 23/07/17 | -5 |
| 4.6.0 | 10/12/17 | 08/12/17 | -2 |
| 4.9.0 | 27/08/18 | 30/07/18 | -28 |
| 4.9.1 | 28/08/18 | 27/08/18 | -1 |
| 5.2.1 | 24/01/19 | 23/01/19 | -1 |
| 5.3.1 | 27/02/19 | 08/02/19 | -19 |
| 5.4.0 | 28/02/19 | 03/04/19 | 34 |
| 5.6.1 | 16/05/19 | 14/05/19 | -2 |
| 5.7.1 | 06/06/19 | 04/06/19 | -2 |
Moreover, the source code is always (except one time) released previous of the corresponding binary.
Please include the missing versions ( https://www.apkmirror.com/uploads/?q=telegram ) that were never released as source-code in the table, as this changes the picture a bit.
Anyway, I don’t see any damage done by that text, given the way Telegram treats the open source client.
If they keep up with this (point releases open source drops at the same time with Play publishing) for 6-12 months I’d feel that the text is indeed not needed. 
@erotavlas Notwithstanding decisions made upstream, maybe you are not helping as much as you could to get it released faster?
Please include the missing versions ( https://www.apkmirror.com/uploads/?q=telegram ) that were never released as source-code in the table, as this changes the picture a bit.
You are right, in the past they did not release the source code frequently.
Anyway, I don’t see any damage done by that text, given the way Telegram treats the open source client.
If they keep up with this (point releases open source drops at the same time with Play publishing) for 6-12 months I’d feel that the text is indeed not needed.
I agree with you
What could I do in order to help the process?
FYI 5.7.1 is alreaady available, pull to refresh.
Cool. Will update anytime today. Thanks!
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.