Skip to content
This repository has been archived by the owner on Aug 22, 2021. It is now read-only.

Release of 0.6.0 #58

Open
lppedd opened this issue Jun 29, 2020 · 9 comments
Open

Release of 0.6.0 #58

lppedd opened this issue Jun 29, 2020 · 9 comments

Comments

@lppedd
Copy link

lppedd commented Jun 29, 2020

Hi Oleg!
I was just wondering when you plan to release 0.6.0, which I see is in the development branch.
I'd like to try and port some bot's code to the JVM, but it seems 0.6.0 includes many differences with 0.5.0, and I don't want to start writing and then "fix" the code again.
Don't worry btw, I don't want to put pressure on you, since you probably have other things to do.

Thanks!

@whyoleg
Copy link
Owner

whyoleg commented Jun 29, 2020

Hi
I'm afraid to give you some ETA, but I believe it will be ready in 1 or 2 weeks... Now, I'm mostly waiting for release of kotlinx-coroutines with support of SharedFlow to replace current updates flow, so it will be more efficient and fast. If no release will be in coming weeks, I will just release with what it is with some experimental annotation which will be removed in 0.6.1 just after release of coroutines..
BTW, I will prepare maximum slightly migration as I can do with Deprecated annotation. You will just need to change some dependencies in gradle and do quick fixes using IDEA - should be really fast.
The main problem for now, is that 0.5.0 support tdlib only up to 1.5.4, but now latest is 1.6.5 (or smth like this). 0.6.0 will contain all latest releases up to latest on moment of release.
So if you start now, you will need to do 2 migrations: from 0.5.0 to 0.6.0 and from 1.5.4 to 1.6.x version.
Or you can just wait a little :)

@lppedd
Copy link
Author

lppedd commented Jun 29, 2020

Thanks for the super-fast answer.
I have no problem waiting, don't worry. Currently I'm experimenting with the raw Java bindings to gather some experience. Previously I was using Python and Pyrogram to build bots, just for some context.

@whyoleg
Copy link
Owner

whyoleg commented Jun 29, 2020

Answering is much faster, then writing code :)
BTW, you can experiment with current 0.5.0. Main interface of interaction will not change in a big way.
0.6.0 is mostly infrastructure, api stabilization and preparation for future multiplatform support (after that, I expect no big backward incompatible changes)
So just experiment with it, it will be easier to migrate later.
If you are interested, there is a preview of changelog in develop branch (it's a little outdated, but main points are there)

@lppedd
Copy link
Author

lppedd commented Jun 29, 2020

Just wanted to let you know release 0.5.0 works nicely (with the JAR-shipped binaries).
I only had to add the OpenSSL DDLs to the path.

@whyoleg
Copy link
Owner

whyoleg commented Jun 29, 2020

@lppedd cool! Good catch about DLLs, I haven't checked it earlier, someone also falls into that issue. During release phase I will also try to do smth with it, so using on clean systems will also work, or at least provide better error handling

Will keep that issue opened until release. If you will find any issues, please post it here, so I will be able to fix it.

@lppedd
Copy link
Author

lppedd commented Jul 2, 2020

@whyoleg Hi!
Was just wondering, where is the event https://core.telegram.org/constructor/updateNewChannelMessage ?
Seems missing from the updates API.

@whyoleg
Copy link
Owner

whyoleg commented Jul 2, 2020

Hi
This library is wrapper over tdlib, not raw telegram api
So you should look here:
Tdlib docs
Available classes and functions

The only thing, is that site contains info for 1.6.0 version or tdlib, but current version of lib supported is 1.5.4

@lppedd
Copy link
Author

lppedd commented Jul 2, 2020

@whyoleg Thanks! Now it's clear, I also checked the generated Java TdApi and there is no such Update.

@whyoleg
Copy link
Owner

whyoleg commented Jul 13, 2020

@lppedd FYI release is postponed, as I decided to rework some things a little (which cause big refactoring). So Im not sure now, how long it will take. The idea is to make 0.6.0 as first step to freeze core API, so I want to invest more in it.
Thanks for waiting it and understanding...

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants