Replies: 2 comments 1 reply
-
|
Take a look at #69 for some earlier discussion. I’m open to pushing the version forward. I think the API is fairly stable at this point but if you compare this to Temporal we are missing some stuff like versioning and continueAsNew. Would love to hear your thoughts. |
Beta Was this translation helpful? Give feedback.
-
|
Sorry for starting a fresh discussion on this one. Thanks for coming back so quickly. I'm still getting my head around the depths of temporal and their docs to understand the use cases for various abstractions. That being said, what's already here is quite powerful. I've gone through all the discussions and it seems like you cater for most people's immediate use cases. I guess the question is do you think you'll need breaking changes in order to support the additional features - if not, i'd suggest just going version 1 to broaden the set of feedback you're getting back. Worst case, you make breaking changes later and release a 2.0 version with good change logs. Best case, the additional functionality requires no breaking changes and you tag 1.1 / 1.2 etc. A major version bump isn't a huge issue but minors + fixes signal a lot more clearly for users that they can upgrade without worrying about breaking api changes. Amazing work by the way, thank you for putting in the time and effort! |
Beta Was this translation helpful? Give feedback.
-
|
https://github.com/laravel-workflow/laravel-workflow/releases/tag/1.0.0 Woohoo!!! Congratulations @rmcdaniel! |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Package and docs look great.
Only real concern about using in prod is no 1.0 tag.
Looks like releases have slowed a bit and no open issues. Anything holding a 1.0 release up?
Beta Was this translation helpful? Give feedback.
All reactions