-
Notifications
You must be signed in to change notification settings - Fork 28
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
Project availability ? #11
Comments
Technically we are ready to launch. We need the last formal decision from the owner of the software to start the open source project. We expect it to happen in late Q3 or early Q4. |
Great I will keep an eye out for it👍
…On Wed, 19 Aug, 2020, 3:19 pm Markus Rothmueller, ***@***.***> wrote:
Technically we are ready to launch. We need the last formal decision from
the owner of the software to start the open source project. We expect it to
happen in late Q3 or early Q4.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#11 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/APRKUHSJUF7LMJ22WN5EBQ3SBON3JANCNFSM4QD4AGIQ>
.
|
Hi @MarRothm, I am also interested in this project. Do you have any idea on the release timeline yet? Will you be able to offer support on this release? Has this system been used in production? |
Hi @tjohannvr! thanks a lot for your interest in this project. As @MarRothm mentioned in the previous comment we are working on getting the final formal decision from the owner to get started. Personally I guess that we will hit live in Q4 this year. |
The project's initial contributor has finished the formal internal and external vetting process. No showstoppers have been identified. We are awaiting now the final Go decision. I'm sorry that we cannot announce any date. Be assured that we are pushing hard. |
Hi ,
Is it happening soon ? Any idea about time lines .. eager to see this .
…On Mon, 16 Nov, 2020, 5:01 pm Markus Rothmueller, ***@***.***> wrote:
The project's initial contributor has finished the formal internal and
external vetting process. No showstoppers have been identified. We are
awaiting now the final Go decision. I'm sorry that we cannot announce any
date. Be assured that we are pushing hard.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#11 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/APRKUHV7LV5QVP64A5EF4ZDSQEEQXANCNFSM4QD4AGIQ>
.
|
what is the progress so far as we have reached a new year. looking forward |
Hello, we are thrilled that there is so much interest in this project. We are still waiting for the final Go decision like @MarRothm mentioned in mid november. Btw a happy new year and see you soon! |
Any updates on new dates |
Yes waiting too .
…On Thu, 4 Feb, 2021, 11:48 pm coregopal, ***@***.***> wrote:
Any updates on new dates
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#11 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/APRKUHTT4CQ6JQSDOIEUYKDS5LQGZANCNFSM4QD4AGIQ>
.
|
Sorry for repeating ourselves. No timeline info possible. Owner is struggling to take the final step. Albeit, we keep fighting for the project. |
keep waiting... |
1 similar comment
keep waiting... |
any news ?????????? |
No
… Am 24.04.2021 um 14:48 schrieb mujumdaraditya ***@***.***>:
any news ??????????
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
You guys keep building suspense here :D |
We‘re sorry! It looks that the project lost important sponsorship. As of now, it is likely we have to cancel it.
Markus
… Am 27.05.2021 um 17:56 schrieb Jose Mendoza ***@***.***>:
You guys keep building suspense here :D
Also interested. :)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
Any plans to release the source? |
When this project is going to be available ?
The text was updated successfully, but these errors were encountered: