[[!meta title="Committing to Master"]]

Committing to the [[master branch|branches]] of the Moonshot master repository has the following affects:

1. Kicks off a new build of the Moonshot software to confirm everything builds.  At this time, the results of this build are unused.

1. Updates the recommended software for people building from source.  We recommend folks building from source use our master branch.

1.  Triggers a Centos build.  This may make new RPMs available; see [[Centos packaging|release/centos]].

# Commit to the subproject

Commit all the desired changes to the submodule.  Use the appropriate branch for Moonshot development:

* master for things that are native to Moonshot
* moonshot for Shibboleth and things we fork
* tr-integ for freeradius

# Update Upstream Version?

Consider updating the upstream version number in configure.ac.  It's in the call to AC_INIT.  :If the upstream version is incremented then set the release back to 1 in the [[spec file|centos]].

# Make sure to push

Make sure to push the submodule.  The build will break if you do not.

# Update master repository

Add the submodule; commit and push the master repository.  Se the bottom of [[branches]] for more details.
# Monitor the build

Take a look at the [buildbot](http://www.project-moonshot.org/buildbot/builders/) to see if the build succeeds.