Mark Constable wrote:
Using Git means developing in branches and keeping trunk stable is possible so a continuous rolling release from a persistent source URL can work.
Please - not another "production-quality" project that only uses code repository checkouts in place of releases.
I've never seen this work successfully. No two users end up running the same code. The code can't possibly be as stable after merging in some huge branch as it was the day before.
Now, if the URL you mention is tied to EXACTLY one version of the source, that would be better. That is essentially a release under a different name.
I can't see the sorts of people who would use something as robust as DSPAM wanting to know that they're the only person on the planet using a particular release of the code.
ALL code has bugs. A release process simply makes it easier to track what those bugs are and manage them separately from new features...
!DSPAM:1011,48330138150921016616567!
