This is mostly a question for the package developer, but if anyone has thoughts on the subject, please feel free to comment as well.
uSync looks very nice, and it's something we could potentially use across several websites, but as we would be building a workflow around this plugin, I'm concerned about futureproofing/future support, particularly as a free plugin relative to Concierge which has the direct backing of the Core team.
Is there anything specific that could reassure us that this package is going to be supported for years to come?
I suppose it's difficult for me to answer what I will be doing with uSync in 3-4 years time, but then again it's hard to predict where anything will be in that time : )
I suppose all I can say, is that I am committed to supporting uSync until at least v8 of umbraco is released.
<speculation> With v8 the core team may release Umbraco Deploy, Which will likely do a lot what usync does. If this does functionally replace uSync then there will be no need for it to continue, but if it doesn't then likely uSync will continue past v8
</speculation>
In the meantime uSync has been around for the last 3 1/2 years and working version has existed for every version of umbraco from v4.10 through to 7.4.3.
Support for new versions of umbraco usually come out within a week or two of the umbraco release, and of course the code is open source, and other people can and do contribute.
Thanks for your reply. The fact that you replied to this, and quickly, is encouraging.
As for Umbraco Deploy, I've looked at the v8 roadmap, but I've never heard of Umbraco Deploy before. Is there any public information on it? Where did you hear about it?
As I understand it Umbraco Deploy will be the Core hooks/apis for packages such as uSync and Courier to use rather than a direct replacement of either but time will tell!
Future Support of Package
This is mostly a question for the package developer, but if anyone has thoughts on the subject, please feel free to comment as well.
uSync looks very nice, and it's something we could potentially use across several websites, but as we would be building a workflow around this plugin, I'm concerned about futureproofing/future support, particularly as a free plugin relative to Concierge which has the direct backing of the Core team.
Is there anything specific that could reassure us that this package is going to be supported for years to come?
Thanks,
David
Hi
I suppose it's difficult for me to answer what I will be doing with uSync in 3-4 years time, but then again it's hard to predict where anything will be in that time : )
I suppose all I can say, is that I am committed to supporting uSync until at least v8 of umbraco is released.
<speculation>With v8 the core team may release Umbraco Deploy, Which will likely do a lot what usync does. If this does functionally replace uSync then there will be no need for it to continue, but if it doesn't then likely uSync will continue past v8</speculation>In the meantime uSync has been around for the last 3 1/2 years and working version has existed for every version of umbraco from v4.10 through to 7.4.3.
Support for new versions of umbraco usually come out within a week or two of the umbraco release, and of course the code is open source, and other people can and do contribute.
Thanks for your reply. The fact that you replied to this, and quickly, is encouraging.
As for Umbraco Deploy, I've looked at the v8 roadmap, but I've never heard of Umbraco Deploy before. Is there any public information on it? Where did you hear about it?
Thanks,
David
Umbraco Deploy has been mentioned at a couple of events - UK Festival and Codegarden - https://video.twentythree.net/the-future-of-umbraco-core (28mins in)
I have spoken to the member of the core team who is building it - we have many of the the same issues :-)
what isn't 100% clear is how it will be released but i think it will be free.
Awesome, really appreciate the info! Thanks.
As I understand it Umbraco Deploy will be the Core hooks/apis for packages such as uSync and Courier to use rather than a direct replacement of either but time will tell!
is working on a reply...