This repository has been archived by the owner on Jul 3, 2020. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 111
What is the plan of 3.0 release? #385
Comments
Besides documentation I believe is it pretty much ready. I won't mind a 3 (pre)release either What shall we do? |
We can release alpha 1 and bring missing stuff then.
…On Thu, Apr 5, 2018, 15:15 Bas Kamer ***@***.***> wrote:
Besides documentation I believe is it pretty much ready. I won't mind a 3
(pre)release either
What shall we do?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#385 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAYEvIZ3dJoQkv67a2adhtD4QD-nbFluks5tlcSSgaJpZM4TH7eb>
.
|
Ok, sounds like a plan. I don’t expect the api to change anymore, but an alpha might attract some more users to test the thing
… Op 5 apr. 2018 om 09:16 heeft Sascha-Oliver Prolic ***@***.***> het volgende geschreven:
We can release alpha 1 and bring missing stuff then.
On Thu, Apr 5, 2018, 15:15 Bas Kamer ***@***.***> wrote:
> Besides documentation I believe is it pretty much ready. I won't mind a 3
> (pre)release either
>
> What shall we do?
>
> —
> You are receiving this because you are subscribed to this thread.
> Reply to this email directly, view it on GitHub
> <#385 (comment)>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/AAYEvIZ3dJoQkv67a2adhtD4QD-nbFluks5tlcSSgaJpZM4TH7eb>
> .
>
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.
|
sounds good to me |
so if everyone agrees maybe someone can tag release? |
"just did it" |
thanks |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Soon I will need this module for a new project and would like to know what is holding 3.0 release or when it will be released. I will use it with zend-expressive and would be a lot easier to do it than with 2.0
The text was updated successfully, but these errors were encountered: