-
Notifications
You must be signed in to change notification settings - Fork 101
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
Recommend BestieTemplate instead? #478
Comments
I am yet to actually try it, so I would feel a bit funny about recommending it. |
@gdalle, we are ready for the next step. @oxinabox, we can have a slow rollout, if you prefer. E.g., announce the intention on Discourse asking for user of PkgTemplate to try Bestie, and if nothing is terrible after a few days/weeks, we proceed with the warning. It should give you time to try and decide. But I am also happy to wait, there is no rush in our side. |
I haven't tried it myself for a new package, I just went over the features with Abel. Let's wait until Frames and I have taken it out for a spin, and then we'll announce the switch |
Moving this here from #483
|
Hi @pat-alt, some answers while my tests are running:
You can accomplish 2.1 using Let me know if the answers make sense or if you need more details. |
Thanks a lot for the quick response @abelsiqueira, this all makes sense! I'll come back to this as soon as I can. |
As discussed at JuliaCon with @oxinabox and @abelsiqueira, we would like BestieTemplate.jl to become the new PkgTemplates.jl, mainly because of its update functionality (you don't have to re-create a package from scratch to get the latest features).
Should we put a big warning on the README here and redirect? That way development efforts will be focused in one place. Abel can you handle the load? Frames would that be okay with you?
The text was updated successfully, but these errors were encountered: