Swagger-codegen: [QUESTION] 2.3.0 Release Date

Created on 31 May 2017 · 15Comments · Source: swagger-api/swagger-codegen

Hi!

According to the README file the release for 2.3.0 was expected for Apr/May 2017. Could you please give me an estimate when the build 2.3.0 will become the stable one?

Thanks!

Question

Source

nirvik66

Most helpful comment

Hi guys, I'm aiming a release before the end of this year.

Will keep you guys posted.

wing328 on 14 Dec 2017

🎉7

All 15 comments

@nirvik66 thanks for the question but I'm sorry to inform you that the release has been postponed.

I'll go through all the remaining issues in the next couple of days and come up with a list of outstanding items pending for 2.3.0.

wing328 on 2 Jun 2017

Thanks for letting me know!

nirvik66 on 2 Jun 2017

Are we closer to a 2.3.0 release?

natami on 19 Jun 2017

same question here :)

rompic on 27 Jun 2017

~~We hope to release by the end of July, 2017~~

wing328 on 27 Jun 2017

UPDATE: We now have a workflow to publish a SNAPSHOT of 2.2.3 and 2.3.0 as part of the CI (travis). Please refer to https://github.com/swagger-api/swagger-codegen#compatibility for more information.

wing328 on 2 Jul 2017

2.2.3 (not 2.3.0) has been released. We hope to release 2.3.0 by the end of Aug as there're some ongoing work to refactor some of the API clients.

wing328 on 17 Jul 2017

Thanks for the update! Looking forward to the release.

rompic on 17 Jul 2017

Hi there, just wondering if we have an update on this :)

Thanks!

dougbacelar on 25 Aug 2017

Hey, also wondering what the status is on the 2.3.0 release

johnnyxh on 6 Oct 2017

👍7

@wing328 Any update on 2.3.0 release

cjkumaresh on 14 Nov 2017

Would love to see the 2.3 release make it out into the world!

Lack of easily-configurable connection pool maxsize in the current python client code gen is putting a damper on my day.

Wish you all a swift and bug-free stable release cutting! And sorry for the issue-spam, really appreciate the open source work you all do.

sherbondy on 15 Nov 2017

+1 on this. The 2.3.0 release will include the OpaqueToken -> InjectionToken update, needed for Angular 5; right now I'm having to hack that into place.