Hi John, > You can keep your project in binary mode (even keep it in version 17) and > still take advantage of version 18, project mode, and git.
Interesting idea. > "Master" branch is version 17. Did you create the v17 Master Branch by: 1) Open a copy of the v17 structure and then open the copy in v18 to convert v17 to v18; and 2) Commit the conversion to v18 as the v17 Master branch; and 3) Create a new branch (off Master) as v18. The above was done only once. > When I want to commit a new version I have a 4D method that copies the > structure, opens it in 4D 18, and then exports the structure in project mode > format. Are you doing this workflow to continue development in v17? 1) Continue to develop in v17; and 2) Make a copy of the v17 structure and then open the copy in v18 to convert v17 to v18; and 3) Commit the v18 to the v18 branch. Best regards, Jeremy French Full post from John DeSoi follows: > When I want to commit a new version I have a 4D method that copies the > structure, opens it in 4D 18, and then exports the structure in project mode > format > On Jan 4, 2020, at 12:33 PM, John DeSoi via 4D_Tech <4d_tech@lists.4d.com> > wrote: > > You can keep your project in binary mode (even keep it in version 17) and > still take advantage of version 18, project mode, and git. Here is what I'm > doing. > > "Master" branch is version 17. When I want to commit a new version I have a > 4D method that copies the structure, opens it in 4D 18, and then exports the > structure in project mode format. This can be completely automated and only > takes a few seconds. > > Now that you have a master branch, you can create a version 18 branch for > implementing next version features that take advantage of new 4D 18 > capabilities. Just open your source directly in version 18 project mode. You > can test the conversion and have both 17 and 18 versions open at the same > time as long as you have separate data files. > > You can continue to make version 17 changes, export, and then merge into your > 18 branch. At some point in the future, all your conversion issues will be > resolved and you can promote the 18 branch as master and deploy with 4D 18. > > John DeSoi, Ph.D. ********************************************************************** 4D Internet Users Group (4D iNUG) Archive: http://lists.4d.com/archives.html Options: https://lists.4d.com/mailman/options/4d_tech Unsub: mailto:4d_tech-unsubscr...@lists.4d.com **********************************************************************
