Re: Git, RDi, etc.

On Fri, Jul 15, 2022 at 8:26 AM Jim Oberholtzer <midrangel@xxxxxxxxxxxxxxxxx>
wrote:

We have:
Git installed from the Open Source Package Management,
Gitbucket installed on that same system. Works well, starts slow but once
it's running works fine.
eGit installed in RDi.

Excellent, Ô Pioneer!

So now the question is what should the process be to manage the source?
(object management, change control, is a different topic)

Git project management is a highly evolved workflow.
It really depends on what you are doing.

- Is this Jim alone, or do you have a team?
- Are you continually updating current to the next release or
maintaining previous releases?
- Do you have one project or multiple projects?

And so on and so forth.

A few notes:

- You can create new repos in a few seconds and push them to your
(hopefully well backed up) origin.
- All repos are idempotent and peer even to the upstream repo: they're
just clones of one another.
- Ongoing development typically works in branches, even nested branches,
that eventually are merged to the next branch up in the nested hierarchy or
discarded.
- If your Gitbucket setup supports pull requests, learn to use pull
requests.


Then again since this is all new to me, I may have a somewhat naive view of

the process. Thoughts?

Git with an upstream environment like Gitbucket/Bitbucket/Gitlab/Github is
sufficient to maintain any modern software project, with the accompanying
complexity. In a few years, you'll start feeling comfortable with that
methodology!