On Tue, Mar 6, 2018 at 12:09 PM, David A Case <david.case.rutgers.edu>
wrote:
> Hi everyone:
>
> We are about to make futher steps toward the April release. Please try
> to get things committed real soon, and follow this instruction:
>
> ***Please don't commit (for now) anything to the master branches at either
> git.ambermd.org or at github.com/amber-md that you don't intend for the
> upcoming April release.***
>
> In a couple of days, I'll create an amber18-with-patches directory,
> which will be the branch from which release-candidate tarballs are
> created. At some point, I'll replace the submodules with their actual
> contents (so that amber18-with-patches won't use submodules any more.)
> [Jason: are there gotchas I should think about at this step?]
>
I'd recommend converting them into subtrees on the release branch. It's a
more automated (and I suspect therefore robust) approach -- there's a SO
thread that has a script that does this:
https://stackoverflow.com/questions/28215244/convert-git-submodule-to-subtree
Use Nikita240's answer (since it pulls the correct commit). I haven't run
the script myself, but the steps are what I'd expect to do the job.
After that point, I'll be (carefully?) cherry-picking what goes into
> amber18-with-patches. But it still adds extra work (and more chance for
> error) if there are commits that should not be cherry-picked. Besides, I
> hope people are concentrating for the next month just on issues related to
> the release. I'll let you know when we can go back to master commits that
> go beyond the current release.
>
Jamie currently has my Amber building on my Jenkins server (
http://www.jasonswails.com:8888). I will send you a login in a separate
email so you can visit the page. You're welcome to add a nightly job to
run a full test suite (Jamie may be able to help here). I haven't paid
much attention to how Jamie has set things up, but it'll obviously need
some changes if you remove the submodules in the release branch.
It can be a matrix build to test both CMake and non-CMake builds. It can
also be set up to send emails in the case of broken builds (and the machine
has GCC, Intel, and PGI compilers available -- all with mpich2 or openmpi
-- to test many compilers). There's also a Windows slave, but I have yet
to get a Mac back on the cluster yet (if someone has one with a public IP
address they'd like to configure as a Jenkins slave, I'd be more than happy
to help them set it up).
Best of luck with the release!
Jason
--
Jason M. Swails
_______________________________________________
AMBER-Developers mailing list
AMBER-Developers.ambermd.org
http://lists.ambermd.org/mailman/listinfo/amber-developers
Received on Tue Mar 06 2018 - 20:00:03 PST
