Issue #700

_posts/2024-06-02-700.md

@@ -0,0 +1,22 @@
+---
+title: DEVOPS WEEKLY ISSUE \#700 - 2nd June 2024 
+date: 2024-06-02T12:00:44+01:00
+---
+
+Devops Weekly is going to take a break.
+
+For more than 13 years I’ve been sending this newsletter every Sunday. It’s given me a unique viewpoint as devops grew from a small community to an international movement and beyond. The first issue was sent a little after the Hamburg devopsdays event back in 2010. Hamburg was the 4th such event, since then more than 500 devopsdays events have happened around the world.
+
+Coming to a milestone like 700 issues allows for a bit of taking stock. I’ve often been asked how I’ve kept doing the Devops weekly newsletter consistently, every week, for so long. Some of that is just stubbornness in fairness, but it takes time every week. I’ve decided for now to use that time for other things.
+
+For now, I’m not sure whether the newsletter will be back in the future or not. But you never know.
+
+Thanks to everyone who’s ever sent me a blog post or a new tool they’ve worked on. Thanks to the companies that have sponsored the newsletter, or chosen to list jobs. Thanks to the event organisers who have built the community. And finally, thanks to all the readers of the newsletter, especially those who’ve sent me messages over the years to say Thanks.
+
+Thanks for being part of Devops Weekly.
+
+Gareth
+
+
+
+

originals/700.mail.txt

@@ -0,0 +1,41 @@
+Subject: =?utf-8?Q?Devops=20Weekly=20#700?=
+Date: Sun,  2 Jun 2024 11:00:44 +0000
+
+DEVOPS WEEKLY
+ISSUE #700 - 2nd June 2024
+
+Devops Weekly is going to take a break.
+
+For more than 13 years I=E2=80=99ve been sending this newsletter every Sun=
+day. It=E2=80=99s given me a unique viewpoint as devops grew from a small=
+ community to an international movement and beyond. The first issue was se=
+nt a little after the Hamburg devopsdays event back in 2010. Hamburg was t=
+he 4th such event=2C since then more than 500 devopsdays events have happe=
+ned around the world.
+
+Coming to a milestone like 700 issues allows for a bit of taking stock. I=
+=E2=80=99ve often been asked how I=E2=80=99ve kept doing the Devops weekly=
+ newsletter consistently=2C every week=2C for so long. Some of that is jus=
+t stubbornness in fairness=2C but it takes time every week. I=E2=80=99ve d=
+ecided for now to use that time for other things.
+
+For now=2C I=E2=80=99m not sure whether the newsletter will be back in the=
+ future or not. But you never know.
+
+Thanks to everyone who=E2=80=99s ever sent me a blog post or a new tool th=
+ey=E2=80=99ve worked on. Thanks to the companies that have sponsored the n=
+ewsletter=2C or chosen to list jobs. Thanks to the event organisers who ha=
+ve built the community. And finally=2C thanks to all the readers of the ne=
+wsletter=2C especially those who=E2=80=99ve sent me messages over the year=
+s to say Thanks.
+
+Thanks for being part of Devops Weekly.
+
+Gareth
+
+
+
+If you received this email directly then you're already signed up=2C thank=
+s! If however someone forwarded this email to you and you'd like to get it=
+ each week then you can subscribe at http://devopsweekly.com
+