2020-06-18 - Artifact and job meta data default archive dates changing
Proposal
As detailed in this issue, a change is being made on gitlab.com to archive job artifacts 30 days after creation and job metadata 90 days after creation starting June 22, 2020. We'd like to create a blog to inform customers of the change and the benefits to them.
Checklist
-
If you have a specific publish date in mind (please allow 3 weeks' lead time) -
Include it in the issue title -
Give the issue a due date of a minimum of 2 working days prior -
If your post is likely to be >2,000 words, give a due date of a minimum of 4 working days prior
-
-
If time sensitive -
Add ~"Blog: Priority" label and supplied rationale in description -
Mention @rebecca to give her a heads up ASAP
-
-
If wide-spread customer impacting or sensitive -
Add sensitive label -
Mention @nwoods
to give her a heads up ASAP
-
-
If the post is about one of GitLab's Technology Partners, including integration partners, mention @TinaS
, apply the Partner Marketing label, and see the blog handbook for more on third-party posts -
Indicate if supporting an event or campaign -
Indicate if this post requires additional approval from internal or external parties before publishing (please provide details in a comment)
@parker_ennis - does this meet the requirements to get a ~sensitive
label? I'd appreciate your input on the proposed publish date as well.