1 [[!title "Committing to Master"]]
3 Committing to the [[master branch|branches]] of the Moonshot master repository has the following affects:
5 1. Kicks off a new build of the Moonshot software to confirm everything builds. At this time, the results of this build are unused.
7 1. Updates the recommended software for people building from source. We recommend folks building from source use our master branch.
9 1. Triggers a Centos build. This may make new RPMs available; see [[Centos packaging|release/centos]].
11 # Commit to the subproject
13 Commit all the desired changes to the submodule. Use the appropriate branch for Moonshot development:
15 * master for things that are native to Moonshot
16 * moonshot for Shibboleth and things we fork
17 * tr-integ for freeradius
19 # Update Upstream Version?
21 Consider updating the upstream version number in configure.ac. It's in the call to AC_INIT.
25 Make sure to push the submodule. The build will break if you do not.
27 # Update master repository
29 Add the submodule; commit and push the master repository. Se the bottom of [[branches]] for more details.
32 Take a look at the [buildbot](http://www.project-moonshot.org/buildbot/builders/) to see if the build succeeds.