Question: RFpeptides Branch - Should I clone the branch directly or merge with main for containerization?

Hi team!

I'm looking to build RFpeptides container and noticed that the rfpeptides branch is currently 5 commits ahead and 13 commits behind the main branch. This creates some uncertainty about the best approach for deployment.

Current situation:

• The rfpeptides branch contains RFpeptides-specific functionality not present in main
• The main branch has 13 newer commits with bug fixes and improvements (including recent chain/residue numbering fixes in #398
• Both branches have diverged since commit b44206a

My questions:

1. For RFpeptides usage: Should I clone the rfpeptides branch directly, or is there a recommended way to merge it with main to get both the RFpeptides functionality AND the latest bug fixes?
2. Containerization: Can I safely use the existing docker/Dockerfile with the rfpeptides branch, or are there any RFpeptides-specific container requirements?
3. Branch status: Is the rfpeptides branch actively maintained? Are there plans to merge it into main or keep it as a separate feature branch?
4. Compatibility: Are there any known conflicts between the RFpeptides changes and the recent improvements in main?

Any guidance on the recommended deployment strategy would be greatly appreciated!

Thanks!

Compare the rfpeptides branch with main from their divergence at b44206a, and review the recent numbering fixes in #398. Inspect docker/Dockerfile against the branch to identify any stated container differences; done would be a maintainer-confirmed deployment recommendation covering branch selection, compatibility, and container requirements.