Hi Apollon,
On Wed, Apr 16, 2014 at 11:33:37AM +0300, Apollon Oikonomopoulos wrote:
(...)
> We run a -dev version - not necessarily the latest one, just one that is
> running stable and has no security issues. In general I follow the list
> on a daily basis (not reading through every mail though) and I always
> keep a clone of the git repository around and periodically check the
> output of
>
> git log --grep BUG/ v1.5-dev${my_release}..
>
> for anything serious (especially BUG/MAJOR commits). If anything too
> serious arises, we are willing to cherry-pick changes on top of our
> production version (which is always deployed using debian packages). The
> bugfix commits usually refer to either the commit, or the version that
> introduced the bug, so it is easy to determine whether we are affected
> by the bug or not.
I think you summarized very well how to carefully use a development
version in prod. That requires a bit of care, but with that you can
get both nice features and quick fixes. Someone recently told me that
1.5 had less bugs than 1.4 because I release 1.4 less often... I must
admit that sometimes it's true.
After 1.5 is released, I'd like to switch to a faster and more regular
release cycle with less constraints on the features. A bit like Linux
after all. We'll work with a new feature window and a freeze period,
with pre-defined deadlines. That will certainly improve the rhythm and
remove some frustration that may come from using devel in prod.
Cheers,
Willy
