Forum OpenACS Development: Re: CVS monitoring for OpenACS: fisheye.openacs.org

Collapse
Posted by Jim Lynch on
Thanks Gustaf! I appreciate the explanation!

OK, so the developer tags as (say) oacs-5-7 or openacs-5-7-compat, which causes apms to be built and placed in the filesystem somewhere.

When someone wants to update (say) openacs-5.7 and those packages selected from non-core, these packages are uploaded to the requested machine from the appropriate place in the filesystem, when update-from-repository is fired off from the installing machine.

Question for everyone, if no cvs commands are issued in update-from-repository, would there still need to be changes made to that part?

Another, when update-from-repository is broken, it can be traced back to whether tags were placed on the package before the packages are built?

With cvs, everything is focused on individual files, and for git, it's focused instead on commits. As Victor has put noncore packages in their own git repo, would this make the transition easier?

One thing might make things harder is figuring out how to interpret existing tags as they come from cvs to git in order to figure out which packages to include in the apm repository for a given version of openacs.

-Jim

Collapse
Posted by Gustaf Neumann on
The programmatical changes are only required on the main repository part (openacs.org). Everything done with cvs can be done with git as well, sometimes maybe slightly different. One has much options with git. Do we want/need submodules? What kind of workflows do we want to support, do we recommend? The biggest piece of work is finally documentation. At the end, if we would do everything the same way as before, is the change worth the effort?

We have done to move to git for our learn project several years ago, victors repos are more or less a byproduct of this. We have changed our development workflows as well several times. We have now a feature-branch oriented development, which is for larger projects the way to go, when active development is happening. we have rather the fear that our code base is getting to far apart from plain openacs. however, the interests of an release manager are often different from the interests of an developer.

Collapse
Posted by Dafydd Crosby on
I've already done some patches to improve the APM repositories. If it would be the thing that finally gets OACS to move to Git, I'll happily put in the effort to make another patch so that it will do the APM building from Git.

http://www.openacs.org/bugtracker/openacs/patch?patch_number=918
http://www.openacs.org/bugtracker/openacs/patch?patch_number=919