fix: Updates to proposal 1

[rossf7]

What type of PR is this?

kind/documentation

What this PR does / why we need it:

Update proposal 1 to

• Make releases check weekly instead of hourly. As we feel hourly is too often.
• Use releases endpoint instead of Atom feed
• Use JSON not YAML for projects metadata to avoid need for Go YAML library

Also adds missing link to atom feed.

Which issue(s) this PR fixes:

None

Special notes for your reviewer (optional):

cc @dipankardas011

[dipankardas011]

@rossf7 as you are adding the atom release here may be we can change the purpose of this pr itself if its okay?
and make the necessary changes to accommodate for the jq one
WDYT?

[rossf7]

as you are adding the atom release here may be we can change the purpose of this pr itself if its okay?

@dipankardas011 Yes sure. Done

[dipankardas011]

LGTM

[dipankardas011]

Lgtm

[rossf7]

Updating the spec after pairing session with @dipankardas011 to simplify the design.

Changes are

• We no longer use a github var to store the latest release
• Instead we trigger the pipeline once a day for the latest version of Falco

Not needing to maintain state simplifies and allows us to use bash for the workflow 🎉

@nikimanoledaki @AntonioDiTuri PTAL 🙏

[dipankardas011]

LGTM

[nikimanoledaki]

LGTM 👍

CI is failing with:

Run bash project-trigger.sh
GH_TOKEN not set
Error: Process completed with exit code 20.

Should the trigger script be running on PRs?

[rossf7]

@nikimanoledaki @dipankardas011

Thank you! I'll create an implementation issue for the renaming.

Should the trigger script be running on PRs?

No I think it should only run if there is a change to scripts dir.

Proposed a fix in #109