Skip to content
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

When can we expect the next release? #1787

Closed
rogerluan opened this issue Mar 18, 2020 · 13 comments
Closed

When can we expect the next release? #1787

rogerluan opened this issue Mar 18, 2020 · 13 comments

Comments

@rogerluan
Copy link
Contributor

Hello!

First of all, thanks for this amazing framework. It makes our apps so much smoother!

Our team has been waiting for 2 specific fixes that have already been merged but oddly enough haven't been released yet. So I was wondering:

  1. What's the rationale for you guys to merge a PR, if it's not followed by a release?
  2. When can we expect the next release?

The two PRs we're waiting for are the following:

#1405
#1579

I appreciate any feedback that we can get.

@sgrgrsn
Copy link

sgrgrsn commented Mar 25, 2020

6 months ago @rahul-malik mentioned that we could expect a new release soon, but unfortunately there has been no new release since the 2.8.1 which is 7 months ago.

I've also tried so reach out to ask if there was something we could help with to get the new release out faster, but I haven't heard anything 👎

@rogerluan
Copy link
Contributor Author

Thanks for the input @sgrgrsn !

I guess we'll have to patiently wait, I hope it can be soon enough 🙏

@rogerluan
Copy link
Contributor Author

Still no update 😞

@garrettmoon
Copy link
Member

Hey y'all, sorry for the radio silence. We'll get out a new release next month.

@sgrgrsn
Copy link

sgrgrsn commented May 21, 2020

Hey y'all, sorry for the radio silence. We'll get out a new release next month.

That sounds really good! Let's us know if there's anything we can do to speed up the process.

@rogerluan
Copy link
Contributor Author

@garrettmoon first of all thanks for the update! 🚀

I truly don't mean to rush you since you already gave us an ETA, but I was wondering what's delaying this release, if the features/fixes we're looking for are already in master? Shouldn't a release require simply updating the podspec and pushing the pod?

I'm asking just out of curiosity really, I appreciate the efforts of the entire TextureGroup team! 🙌

@nslogx
Copy link

nslogx commented Jun 19, 2020

Hey y'all, sorry for the radio silence. We'll get out a new release next month.

@garrettmoon Still no update 😞

@garrettmoon
Copy link
Member

@huangjianke we're still on track to get a release out this month as promised!

@nslogx
Copy link

nslogx commented Jun 20, 2020

@huangjianke we're still on track to get a release out this month as promised!

Great, Thanks

@rogerluan
Copy link
Contributor Author

Guys, there's a RC out 🚀 https://github.com/TextureGroup/Texture/releases/tag/3.0.0-rc.1

Thanks @garrettmoon ! Is there anything specific you want us to look for, when testing? Or do we need a v3.0.0 migration checklist, or guide?

@garrettmoon
Copy link
Member

Hey y'all, as promised we're working towards a 3.0 release and have a release candidate out to CocoaPods (RC2).

@rogerluan A 3.0 migration guide is a great idea! I put up a starter doc which I'd love folks to add tips to.

@rogerluan
Copy link
Contributor Author

Thanks for creating the doc! I added my entry to the only breaking change that prevented my project from compiling once I upgraded: #1878

We were also applying 2 changes that were present in past PRs that got merged and released in v3.0, so not we're not applying those changes anymore. That's gif image support, and an issue with fonts defaulting to Times New Roman. I thought it didn't make sense to mention that in the doc, though.

@garrettmoon
Copy link
Member

Thanks y'all, I'm going to close this one out.

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

No branches or pull requests

4 participants