On Jan 4, 2020, at 6:42 PM, John DeSoi via 4D_Tech <[email protected]> wrote: > > Yes. Switch back to the 17 "master" branch. Verify there are no uncommitted > changes in the Project folder (git status called from 4D). Move the Project > folder to the trash. Run the 17 to 18 script again and generate a new Project > folder with the current source. Commit as the new "master" branch. Merge (or > fast forward) the master branch into the 18 branch to keep it up to date with > the changes in 4D 17.
This is an interesting workflow, I’ll probably copy this to start prepping for v18. > In this model, I'm only making structure and form changes in the 17 master > branch. Methods can be changed in both branches. Are there any problems with functionalities can’t be used in v18 project mode that don’t have replacements in v17.3 (not R-series)? I’ve seen mentions of users/groups changes in particular but I haven’t investigated the details yet. Jim Crate ********************************************************************** 4D Internet Users Group (4D iNUG) Archive: http://lists.4d.com/archives.html Options: https://lists.4d.com/mailman/options/4d_tech Unsub: mailto:[email protected] **********************************************************************
