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

Add future of Monofony #518

Merged
merged 1 commit into from
Jan 14, 2025
Merged

Add future of Monofony #518

merged 1 commit into from
Jan 14, 2025

Conversation

loic425
Copy link
Member

@loic425 loic425 commented Jan 14, 2025

Q A
Branch? 0.10 or 0.11
Bug fix? no/yes
New feature? no/yes
Related tickets fixes #X, partially #Y, mentioned in #Z
License MIT

@loic425 loic425 merged commit 71f637b into monofony:0.11 Jan 14, 2025
12 of 26 checks passed
@loic425 loic425 deleted the deprecate-monofony branch January 14, 2025 08:57
@harikt
Copy link
Contributor

harikt commented Jan 25, 2025

I wasn't aware that monofony itself is deprecated. Also the sylius stack documentation is not very clear what to do and what it do.

@loic425
Copy link
Member Author

loic425 commented Jan 25, 2025

I wasn't aware that monofony itself is deprecated. Also the sylius stack documentation is not very clear what to do and what it do.

Hi, improving the Sylius stack documentation is one of my priorities and we've worked a lot on it. But you're right, we need to bring a big picture of the project goal.

Feel free to ask me some questions on private messages.

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

Successfully merging this pull request may close these issues.

2 participants