Skip to content

Commit

Permalink
docs/RELEASE-PROCEDURE: updated coming releases dates [ci skip]
Browse files Browse the repository at this point in the history
  • Loading branch information
@bagder
bagder committed May 15, 2019
1 parent f778c35 commit 0af41b4
Showing 1 changed file with 4 additions and 1 deletion.
5 changes: 4 additions & 1 deletion docs/RELEASE-PROCEDURE.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -84,8 +84,11 @@ Coming dates
Based on the description above, here are some planned release dates (at the
time of this writing):

- March 27, 2019
- May 22, 2019
- July 17, 2019
- September 11, 2019
- November 6, 2019
- January 8, 2020 (moved)
- February 27, 2020
- April 22, 2020
- June 17, 2020

7 comments on commit 0af41b4

@vszakats
Copy link
Member

@vszakats vszakats commented on 0af41b4 May 16, 2019 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not sure how the proceed from this point, but here is an equivalent (simple to generate) .ics file that (if shared from the website) can be subscribed to from calendar clients, and the dates will update automatically:

curl.ics:

BEGIN:VCALENDAR
PRODID:-//curl//curl Calendar//EN
VERSION:2.0
CALSCALE:GREGORIAN
METHOD:PUBLISH
X-WR-TIMEZONE:UTC

BEGIN:VEVENT
DTSTART;VALUE=DATE:20200617
DTEND;VALUE=DATE:20200617
CLASS:PUBLIC
SUMMARY:curl release
TRANSP:TRANSPARENT
END:VEVENT

BEGIN:VEVENT
DTSTART;VALUE=DATE:20200422
DTEND;VALUE=DATE:20200422
CLASS:PUBLIC
SUMMARY:curl release
TRANSP:TRANSPARENT
END:VEVENT

BEGIN:VEVENT
DTSTART;VALUE=DATE:20200227
DTEND;VALUE=DATE:20200227
CLASS:PUBLIC
SUMMARY:curl release
TRANSP:TRANSPARENT
END:VEVENT

BEGIN:VEVENT
DTSTART;VALUE=DATE:20200108
DTEND;VALUE=DATE:20200108
CLASS:PUBLIC
SUMMARY:curl release (moved)
TRANSP:TRANSPARENT
END:VEVENT

BEGIN:VEVENT
DTSTART;VALUE=DATE:20191106
DTEND;VALUE=DATE:20191106
CLASS:PUBLIC
SUMMARY:curl release
TRANSP:TRANSPARENT
END:VEVENT

BEGIN:VEVENT
DTSTART;VALUE=DATE:20190911
DTEND;VALUE=DATE:20190911
CLASS:PUBLIC
SUMMARY:curl release
TRANSP:TRANSPARENT
END:VEVENT

BEGIN:VEVENT
DTSTART;VALUE=DATE:20190717
DTEND;VALUE=DATE:20190717
CLASS:PUBLIC
SUMMARY:curl release
TRANSP:TRANSPARENT
END:VEVENT

BEGIN:VEVENT
DTSTART;VALUE=DATE:20190522
DTEND;VALUE=DATE:20190522
CLASS:PUBLIC
SUMMARY:curl release
TRANSP:TRANSPARENT
END:VEVENT

END:VCALENDAR

@bagder
Copy link
Member Author

@bagder bagder commented on 0af41b4 May 16, 2019

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I already share an ICS on google calendar:

https://calendar.google.com/calendar/ical/c9u5d64odop9js55oltfarjk6g%40group.calendar.google.com/public/basic.ics

It also shows feature freeze dates.

@vszakats
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That's awesome! I didn't not about it (obviously!). Subscribing now — Thanks!

@bagder
Copy link
Member Author

@bagder bagder commented on 0af41b4 May 16, 2019

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It is also very likely to stay accurate and up-to-date as this is the primary calendar I use when I plan releases and announce feature freezes on the mailing list etc...

@vszakats
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just perfect! I'm tempted to add a link to it from RELEASE-PROCEDURE.md.

@bagder
Copy link
Member Author

@bagder bagder commented on 0af41b4 May 16, 2019

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That is a good idea.

@vszakats
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

#3895

Please sign in to comment.