Who, then, are developers?
--------------------------
+
+[role="incremental"]
* Anyone who writes code for OpenSRF or Evergreen is a developer:
** _Committers_: those who have the ability to commit code to release
branches
Release processes
-----------------
+
+[role="incremental"]
* Evergreen currently creates two
http://evergreen-ils.org/dokuwiki/doku.php?id=versioning[different kinds of
- releases]:
+ releases]:
+
+[role="incremental"]
** Major/minor _feature_ releases (2.0.0, 2.1.0, 2.2.0) - in which new
features are added to Evergreen
** _Patch_ releases (2.0.1, 2.0.2, 2.0.x, 2.1.1) - in which changes are
limited strictly to bug fixes and updated translations
+
+[role="incremental"]
* Evergreen 2.2.0 marks our first attempt to adopt a _time-based_ feature
release
+
+[role="incremental"]
** Instead of defining a release by which features we plan to add, we
define a release as a cumulative sum of all new features which were
considered stable enough to commit to the release branch at a given
* Create, find, and fix bugs
* Communicate
+Communicate - Google Hangout
+----------------------------
+ * Newest form of group communication
+ * Attempted during Hackfest 2012 with underwhelming results
+ * *Extremely* hard to search (impossible?)
+
Communicate - Mailing lists
---------------------------
* Oldest form of group communication: email
** opensrf.xml values
** Catalog / staff client customization
-Communicate - Google Hangout
-----------------------------
- * Newest form of group communication
- * Attempted during Hackfest 2012 with underwhelming results
- * *Extremely* hard to search (impossible?)
-
Developer Glossary
------------------
* _Tuits_, or _Round tuits_ - a fictional device that would enable the