Upgrade to latest version | Process in discussion #5961 | Support Center

ashgadala created 6 years ago

Hi Support,

I am following this link and got this help from couple of users.

I was able to upgrade to newer version including the UI changes with the approach proposed by brandondjmurphy. I am trying to figure out downstream impacts by taking this approach and looking for an adivse.

Let us know, if you agree with either one of the approaches, infact any other approach from the discussion until streamline the upgrade process of UI. If you dont agree. listing the reason would be a great help me.

Apporach by brandondjmurphy

   `I have a master trunk, which only has the original ASPNET Zero source, and
                then a DEV branch which contains my modifications.

                After each release, download new release, copy over the master branch and
                commit. Then merge the updated master into the DEV branch. This is
                relatively painless and is only a little painful when for example the
                metronic folder structures are changed.

                I think there was a article on the forum covering this and this was the
                suggested method.

                B`

Approach by iamseanduffy

        `We have 2 GIT repositories:

        UPSTREAM : Contains the unmodified product that we download from the ASPNETZERO download page
        ORIGIN : Contains our modified version of ASPNETZERO.
        Repository ORIGIN is a FORK of repository UPSTREAM.

        When a new version of ASPNETZERO is released we:

        Delete ALL files from UPSTREAM.
        Re-download the most recent version of from the ASPNETZERO download page (using the same details as used in the original download)
        Check this version into UPSTREAM.
        Tag the version number.
        GIT Merge changes from UPSTREAM into ORIGIN.`

Go to accepted answer

Upgrade to latest version | Process in discussion #5961

4 Answer(s)