63 Results for the search: "#5"
Proposals 28
View all (28)
Events 5
Debates 3
Posts 15
First privacy changes in forms, downloads and emails
Campaign Library - Phase 2- Sprint 5 Delivery
Campaign Library - Phase 2- Sprint 4 Delivery
Campaign Library - Phase 2- Sprint 2 Delivery
Participants 1
Comments 11
I totally love the overall approach, and we already have a cardboard version of the refined Mautibot at our office!!!
My personal opinion is that this does not have to be final, though. The idea of having a "styleguide" or "construction kit" sounds great to me (https://github.com/mautic/low-no-code/issues/31#issuecomment-2950272959)
In particular, I would not understand this voting as "Flavor #5 has to be used for error messages" - rather still be open to more positive and fun variations.
I totally love the overall approach, and we already have a cardboard version of the refined Mautibot at our office!!!
My personal opinion is that this does not have to be final, though. The idea of having a "styleguide" or "construction kit" sounds great to me (https://github.com/mautic/low-no-code/issues/31#issuecomment-2950272959)
In particular, I would not understand this voting as "Flavor #5 has to be used for error messages" - rather still be open to more positive and fun variations.
Hi all, unfortunately we had no community attendees for the demo at the meeting so having waited for 5 or so minutes we drew to a close. If you would like to see the demo please leave a message here and I will pick up with you. Thank you, DJ
Hi all, unfortunately we had no community attendees for the demo at the meeting so having waited for 5 or so minutes we drew to a close. If you would like to see the demo please leave a message here and I will pick up with you. Thank you, DJ
Thanks for sharing your thoughts @joebordes - to be clear, right now we do not support a minor release after the next minor release is made (e.g. when 5.2 comes out, 5.1 is no longer supported), and a major release is supported for 3 months after the next major release. We do a new major release on average, every 12-18 months.
Currently we don't have any LTS release, in the traditional sense. Just an 'actively supported' version.
You can find the timings we currently have at https://www.mautic.org/mautic-releases - we are planning to extend the support that we offer as our core security support to 3 and 6 months respectively, however for many businesses who have tens or hundreds of instances to update even this isn't enough time. They need security releases for Mautic for a while longer, so that they can safely update all their instances while remaining compliant.
That's why we're proposing to offer this (paid) service, which will also be a revenue stream for the project.
I hope that gives a bit more context!
Thanks for sharing your thoughts @joebordes - to be clear, right now we do not support a minor release after the next minor release is made (e.g. when 5.2 comes out, 5.1 is no longer supported), and a major release is supported for 3 months after the next major release. We do a new major release on average, every 12-18 months.
Currently we don't have any LTS release, in the traditional sense. Just an 'actively supported' version.
You can find the timings we currently have at https://www.mautic.org/mautic-releases - we are planning to extend the support that we offer as our core security support to 3 and 6 months respectively, however for many businesses who have tens or hundreds of instances to update even this isn't enough time. They need security releases for Mautic for a while longer, so that they can safely update all their instances while remaining compliant.
That's why we're proposing to offer this (paid) service, which will also be a revenue stream for the project.
I hope that gives a bit more context!
Share