• Stephan (2/2) Mar 02 2012 is it just me or is it irritating that http://dlang.org/changelog.html
• Brad Anderson (15/16) Mar 02 2012 I'm not that bothered by it but I think it'd be better if that weren't t...
• Dejan Lekic (3/5) Mar 06 2012 Seems that you are easily irritated. It takes one click to realise it is...

Stephan <spam extrawurst.org> writes:

is it just me or is it irritating that http://dlang.org/changelog.html 
has a unreleased empty dmd2059 release on top ?!

Brad Anderson <eco gnuk.net> writes:

On Fri, Mar 2, 2012 at 10:17 AM, Stephan <spam extrawurst.org> wrote:

 is it just me or is it irritating that
http://dlang.org/changelog.**html<http://dlang.org/changelog.html>has a
unreleased empty dmd2059 release on top ?!

I'm not that bothered by it but I think it'd be better if that weren't the
case.  The issue could be solved by using release and devleop branches in
git rather than putting everything on master and deploying from master.

I'm in love with Vincent Driessen's approach:
http://nvie.com/posts/a-successful-git-branching-model/

In this model they'd still deploy from a master copy but new changes would
enter through a "develop" branch (often through feature branches/pull
requests) and only be merged into master during a release.  Hotfixes could
be applied to the running website to fix up errors in the current release
using the hotfix branch method.

Master serves as a stable snapshot of the release and develop is the under
construction branch.

Regards,
Brad Anderson

Dejan Lekic <dejan.lekic gmail.com> writes:

Stephan wrote:

 is it just me or is it irritating that http://dlang.org/changelog.html
 has a unreleased empty dmd2059 release on top ?!

Seems that you are easily irritated. It takes one click to realise it is a 
non-released version (everything empty)... :)