I’ve been working on a new 2.0 version of Community Auth, and it’s substantially different than the 1.X version because roles all have their own profile tables in the database. In the 1.X version roles all share a user profile table. Having separate tables allows roles profiles to be unique. For instance, an employee doesn’t really need a shipping address, but a customer might. An employee might need to be in a department, but a admin shouldn’t be restricted to a department. By creating separate profile tables, each role can be easily customized.
What I’ve always done is work out of a directory in htdocs on my dev machine. When I want to commit, I copy the files to the repo, commit and push.
Although I haven’t created the 2.0 branch in the repo yet, I’m ready but I have some questions.
1) Is it standard practice to work out of the repo, or is it “normal” to work out of a different directory and then copy, commit and push? (The way I’ve been doing it). The reason why I’m asking is it seems like a lot of work to do what I’m doing, but working straight out of the repo seems risky for some reason.
2) I don’t know that I want to abandon the 1.X version, meaning I don’t know that I would ever do a merge and be done with 1.X. In this case, is 2.0 a branch, or should it just be a separate repo? I’m not really sure it’s worth hanging on to the 1.X branch, but should I decide to keep working on it, I just want to do the right thing.