Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Set up streams for next and next-devel #283

Closed
5 tasks done
jlebon opened this issue Sep 24, 2019 · 7 comments
Closed
5 tasks done

Set up streams for next and next-devel #283

jlebon opened this issue Sep 24, 2019 · 7 comments
Labels
jira for syncing to jira

Comments

@jlebon
Copy link
Member

jlebon commented Sep 24, 2019

F31 is entering Beta. We should start tracking it in FCOS too, esp. since we're likely to release stable with that content.

Off the top of my head, this needs patches for:

  • fedora-coreos-config to create the new branches
  • config-bot config to manage the new branches
  • coreos-koji-tagger for lockfile handling
  • fedora-coreos-pipeline to trigger the new builds
  • fedora-coreos-browser to display the builds
@jlebon
Copy link
Member Author

jlebon commented Sep 25, 2019

First step to this is in coreos/fedora-coreos-config#180

@jlebon jlebon added the jira for syncing to jira label Oct 17, 2019
@jlebon
Copy link
Member Author

jlebon commented Mar 17, 2020

OK, I forked off testing-devel into next-devel and opened a PR to start tracking the rebase to f32 for that stream: coreos/fedora-coreos-config#306

@jlebon
Copy link
Member Author

jlebon commented Mar 20, 2020

config-bot: coreos/fedora-coreos-releng-automation#88
pipeline: coreos/fedora-coreos-pipeline#211
browser: coreos/fedora-coreos-browser#7

The only remaining thing is coreos-koji-tagger, which will need a bit more work to adapt.

@jlebon
Copy link
Member Author

jlebon commented Mar 20, 2020

The only remaining thing is coreos-koji-tagger, which will need a bit more work to adapt.

Started that in coreos/fedora-coreos-releng-automation#89.

I think we'll also need coreos/fedora-coreos-releng-automation#48 (aka #293) so that we don't have to set up another stream just for lockfile bumping.

@jlebon
Copy link
Member Author

jlebon commented Apr 8, 2020

This is blocked now by #454 and #293.

jlebon added a commit to jlebon/fedora-coreos-pipeline that referenced this issue Apr 9, 2020
There's more work needed before we can unblock those. For background,
on bodhi-updates, see:

coreos/fedora-coreos-config#335 (comment)

For the next-devel stream, see:

coreos/fedora-coreos-tracker#283 (comment)
jlebon added a commit to jlebon/fedora-coreos-pipeline that referenced this issue Apr 9, 2020
There's more work needed before we can unblock those. For background,
on bodhi-updates, see:

coreos/fedora-coreos-config#335 (comment)

For the next-devel stream, see:

coreos/fedora-coreos-tracker#283 (comment)
jlebon added a commit to coreos/fedora-coreos-pipeline that referenced this issue Apr 9, 2020
There's more work needed before we can unblock those. For background,
on bodhi-updates, see:

coreos/fedora-coreos-config#335 (comment)

For the next-devel stream, see:

coreos/fedora-coreos-tracker#283 (comment)
@jlebon
Copy link
Member Author

jlebon commented Apr 16, 2020

Setting up next stream:
coreos/fedora-coreos-config#353
coreos/fedora-coreos-pipeline#225
coreos/fedora-coreos-streams#85
coreos/fedora-coreos-browser#9

@zonggen is working on updating the website.

@jlebon jlebon changed the title Set up streams for branched, next, and next-devel Set up streams for next and next-devel Apr 20, 2020
@jlebon
Copy link
Member Author

jlebon commented Apr 20, 2020

Going to descope this to just next, and next-devel and mark as done since the streams are up now.

The lockfile work pending is already tracked in #293 and #454.

@jlebon jlebon closed this as completed Apr 20, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
jira for syncing to jira
Projects
None yet
Development

No branches or pull requests

1 participant