-
Notifications
You must be signed in to change notification settings - Fork 860
Prisma 1 in maintenance mode & Prisma 2+ ready for production #4898
Comments
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 10 days if no further activity occurs. Thank you for your contributions. |
Can you deliver any documentation of migration form prisma to prisma framework? |
@gustawdaniel Check out the Prisma 2 upgrade guide |
This comment has been minimized.
This comment has been minimized.
Commenting to keep this from going stale. The guide (which is now here) only covers upgrading from the generated client when there are likely a number of people using prisma-binding for the stitching support. Documentation on that upgrade path would be greatly appreciated. |
Is that why so many of the current issues have gone without a response from Prisma? Not to mention questions in the Slack channel going unanswered more often than not as well. I have serious questions as to the level of support users can expect from Prisma 2.0 when they've abandoned users in Prisma 1 so completely prior to Prisma 2.0 being production or even having feature parity with Prisma 1. |
Hey @technicallynick, thanks a lot for your feedback and my apologies for the delayed response times for Prisma 1 related questions – I totally understand your frustration! We are trying our best to help users that are stuck with Prisma 1 issues as well as those who want to upgrade to Prisma 2.0. I also just got back to your subscription issue that you posted here. Unfortunately, we had to reduce our support capacity for Prisma 1 on GitHub and can't respond to most questions unless they're touching on extremely critical bugs that need to get fixed in Prisma 1.
We have recently hired a new Developer Success Engineer who is now taking care of answering questions on Slack, including the ones for Prisma 1! Also, please feel free to ping me directly on Slack (I'm Upgrading to Prisma 2.0In general, I want to emphasize that we're in the process of working out a proper upgrade path for Prisma 1 users! This does take some time since we not only want to help users upgrading with extensive documentation, but we're also building dedicated tools that will ease the transition towards Prisma 2.0! We're still in a research state but we're posting updates about the progress of this in this GitHub issue. Please let me know if you have any further questions or ping me on Slack to discuss the situation directly in a DM or via email! |
This comment has been minimized.
This comment has been minimized.
Two things,
Second, it feels like the sunsetting of Prisma 1 is in a very speedy process based on the site having Prisma 2 completely take over, changing the package name completely from prisma to prisma1 and from the looks of it, not really responding to Prisma 1 questions that well in Slack; however, Prisma 2 seems like it still needs some considerable beefing up before it compares to Prisma 1. I'm not sure I'd want to switch to Prisma 2 for any new projects at this time when major functionality isn't there that Prisma 1 has to offer. Taking away the building up an entire database based off of a schema file is a HUGE deal. That is one of the biggest reasons why I use Prisma so I can spin up a project extremely fast. It was even stated in Prisma Day that Prisma 2 is not quite ready and to continue to use Prisma 1, but it would be great for people to try it out and give feedback. I understand the want to get switched over to the newer version is extremely desired to lessen the amount of maintenance, etc.; however, it would be nice if it were done in a more patient manner and realize that this switch may not be as desired by the developers that use it considering the tradeoffs. |
Hey @Bruqui, thanks a lot for sharing your thoughts! We'll definitely look into the vulnerabilities you pointed out, I'll keep you posted here! Thanks for letting us know 🙏
We do our best to support Prisma 1 users when they're having questions and are raising issues on Slack, but response times unfortunately can be a bit slower since we sometimes need to prioritize issues with Prisma 2.
I fully agree that Prisma Migrate is a crucial feature of Prisma 2! The reason why we've launched without it at first was because it needed some more product and design work before we could publish a first beta. However, I'm really happy that now that Prisma Client is out the door, we have a lot more capacity to focus on Prisma Migrate. Our product team headed by @thebiglabasky and @albertoperdomo is currently looking into Migrate and would love to hear your thoughts on it! It would be a huge help for us if you could define your requirements and use cases for Prisma Migrate in the repo (e.g. how you'd like to use it in CI/CD environments). I'm also sure our product folks would love to jump on a call with you to learn more if you'd be open to it! 😄 Also, although Prisma Migrate is an important feature of Prisma, we definitely see a lot of people use Prisma Client with introspection successfully, in that workflow Prisma Migrate is not needed and developers still get the benefit of Prisma Client's type-safe querying API (or if they're not building critical application, using the experimental version of Migrate).
I'm not sure when this was mentioned but it's not the message we want to send, apologies for the confusion! 🙏 If you're getting started with a new project, we definitely recommend folks to get started with Prisma 2 and not use Prisma 1 – sorry if we said so otherwise at some point during the event 🙂
Can you be a bit more specific where you'd like to see more patience from our end? I'd love to understand better what we can do to support current Prisma 1 users! 🙂 All the documentation and examples for Prisma 1 are still accessible and we have no plans of "sunsetting" anything (also note that Prisma 1 is open source it can't really be "sunsetted" anyways). I hope that helps clarify a few things, please let me know if you have any further questions! 🙏 |
Holy cow!!! That is probably one of the best responses I've ever gotten on a bigger JS library like this. Thanks you!!! I definitely agree In the sense of things feeling rushed is that Prisma 1 is already in the background of the Prisma website. As far as I've found, you have to jump into the docs of the website then click on Prisma 1 to get to anything about it. And for the npm package, Prisma 2 has already taken over the I need to run for now, but I'll come back to this page and see about doing a call if you guys would like. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 10 days if no further activity occurs. Thank you for your contributions. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 10 days if no further activity occurs. Thank you for your contributions. |
Hey everyone 👋
This issue gives a brief update on the development status of Prisma 1 and the new Prisma 2.0.
Prisma 1 is in maintenance mode
We're working hard to push out the first stable release of Prisma 2.0. Unfortunately this requires most of our engineering resources which is why decided to put Prisma 1 into maintenance mode. This means no new features will be developed for Prisma 1. We will however make sure to fix critical bugs and keep supporting current users.
Prisma 2.0 is ready for production
Prisma 2.0 is ready for production use.
Feel free to join the discussion and share your feedback on ideas on the future plans!
The best way to get started with Prisma 2.0 is by following the Quickstart or exploring the ready-to-run examples.
The text was updated successfully, but these errors were encountered: