Question

Photo of Aaron Jones

0

GitHub Migrations

2

Hello,

 We are looking to pull down some of the migrations from GitHub to utilize the calendar feature that was committed. We have went through the developer documentation but haven't found a solid way on how to accomplish this. What is the best approach to doing this? Has anyone else attempted this?

Thank you in advance

  • Jon Edmiston

    Jon Edmiston

    Just a warning on the develop branch it's just that develop. We're are changing and refactoring the code on a daily basis.

    • David Leigh

      David Leigh

      Yes, good point Jon - the develop branch is not really stable enough for a production environment unless you like to live on the edge! The approach we use to get early fixes for production is to pull the latest stable release on "master", and cherry-pick the fixes or features that we need from "develop", test and then deploy to production. This only works for non-breaking changes/fixes though, and we don't add anything that requires a data migration.

      • Photo of David Leigh

        0

        Hi Aaron,

        The only way to access these commits at present is to pull the "develop" branch to your own development environment and then build and deploy it yourself.<br /> The Rock project does not currently have nightly builds that can be downloaded for non-developers, although this might be a good suggestion for the black book for those who are keen to jump in and start testing new features immediately.
        http://www.rockrms.com/Rock/Ideas

        Another thing you could consider is signing up as an Alpha or Beta tester to get early access to these new features. http://www.rockrms.com/GetInvolved

        Hope this helps!

      • Photo of Aaron Jones

        0

        Thank you guys for your direction. We currently are using the SDK and are wanting to add an Event Calendar. I see that this is on the Spark Git Hub and want to create this feature to be compatiable with any Rock update. Is there any direction to follow for creating this feature for our current project?

        • David Leigh

          David Leigh

          As I mentioned previously, I think the best approach would be to pull the "develop" branch to your development environment, build and deploy Rock locally, and develop your SDK to be compatible with that local build of Rock. This will ensure that you are building your add-on against the changes that will be released in v4, including the Event Calendar. Just be aware, as Jon pointed out, that the develop branch changes frequently and is not guaranteed to be stable - which is OK if you are also doing development work, not deploying to production.