Request for approval: deploying dlang.org on merge

[Andrei Alexandrescu via Digitalmars-d]

On 5/26/16 11:53 AM, Seb wrote:
> Hey,
>
>
> Let me tell you a little story - once there was the amazing Dconf at the
> beginning of this month (4-6.5).
>
> We put a notice about it on dlang.org "DConf 2016 is coming up: May 4-6
> in Berlin, Germany. Secure your seat before it's sold out!".
>
> It took two weeks, but finally karthikeyan had the time to shout and
> report the outdated message [1].
>
> The PR was merged subsequentially quite fast, but this was more than a
> weeek ago and we still have the annoucement about DConf on our landing
> page.
>
> I talked with CyberShadow a bit, because setting up a CI and deploying
> the website automatically on a merge doesn't seem difficult and to quote
> him the main problem is approval:
>
>> We already have
>> http://wiki.dlang.org/User:Vladimir_Panteleev/Website_staging so it's
>> not a matter of implementation, just everyone agreeing that it's what
>> we want to do
>
> Imho it makes a lot of sense to do this, because showing such horribly
> (>=more than three weeks) outdated news on dlang.org makes a terrible
> impression and merging something should be the approval, not the huge
> latency of our dlang.org maintainer (no offense).
>
> If you are against this automatic deployment or want to do it manually
> yourself, please shout now.
>
> [1] https://issues.dlang.org/show_bug.cgi?id=16040
> [2] https://github.com/dlang/dlang.org/pull/1304

If Vladimir is okay with auto-deployment I'm okay too. Move fast! The 
only question is, how do we avoid cases in which a deployment breaks 
something important? -- Andrei