X-Git-Url: http://www.project-moonshot.org/gitweb/?p=devwiki.git;a=blobdiff_plain;f=release%2Fmaster.mdwn;fp=release%2Fmaster.mdwn;h=ff3615dde6de93f6d0a6b28496bcbe26b5c9c6b1;hp=0000000000000000000000000000000000000000;hb=8dab342fe480418e540b94fbdf1f294f2f167b19;hpb=9a33216d570d8afe222b3e5dbe6cf2db0259de2f

diff --git a/release/master.mdwn b/release/master.mdwn
new file mode 100644
index 0000000..ff3615d
--- /dev/null
+++ b/release/master.mdwn
@@ -0,0 +1,32 @@
+[[!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.
+
+# 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.