org/meetings/2014WinterDevMeeting/notes/TorReleaseProcess.md

-= Little-t tor release process =
+# Little-t tor release process
 
-'''Abstract:''' How can we make better software faster and get it into our users hands faster.
+**Abstract:** How can we make better software faster and get it into our users hands faster.
 
-== Minutes ==
+## Minutes
 
-=== Little-t-tor release plans ===
+### Little-t-tor release plans
 
-Want more frequent Tor point releases, ''and'' want more frequent stable release series
+Want more frequent Tor point releases, _and_ want more frequent stable release series
 
 Earlier, we decided Nick would do releases too. But in practice he didn't.
 
@@ -16,7 +16,7 @@ Two things dissuading Nick from doing Tor releases:
 
 (In 0.2.5.2-alpha, Roger basically rewrote all the changes entries to be user-facing and user-useful.)
 
-=== Timing and triage of tickets ===
+### Timing and triage of tickets
 
 Need a process for what goes into each stable release
 
@@ -30,7 +30,7 @@ So the solution is, more people fixing bugs? Or what?
 
 Need a category in between undecided and "the upcoming stable"
 
-=== For the future ===
+### For the future
 
 Cannot pick all three of:
 - People working on it