#118 Reducing the complexity of the scheduling format
Opened 2 years ago by siosm. Modified a year ago

It's unclear to me where this format is used (beyond people referring to it directly) and who rely on the format staying as is.

Thus it would be interesting if we could consider moving to another format that is simpler to maintain, edit and update.

See: https://pagure.io/fedora-pgm/schedule/pull-request/116


Hi @siosm

I agree with your suggestion to consider moving the scheduling format to something easier to edit and understand, however I will be super honest and transparent - this is something I don't have the capacity to attempt to change right now. The main reason being my priority is to get very comfortable with the current way things are done when administrating and maintaining release schedule before I could even consider what alternatives or changes I could and should make. It will come as no surprise to you that there are many things in the Fedora project that would seem have no obvious dependencies, but they are usually there, somewhere in the layers of integration! :)
I think once I know this workflow in depth, and understand how this release schedule is embedded in the release process, this is definitely something I will revisit.
I just wanted to be honest with you though that this idea is something I just cant give any attention to for a while.

You're welcome to leave this ticket open or close it, entirely up to yourself, and thank you for validating something that I was wondering about, but just not in a position to change right now.

Thanks for the thoughtful response here. I definitely agree with what you said. Let's keep it open even though I understand that it's going to be for later. We fixed our immediate issues by moving to using Bodhi for EOL dates so this is less of an issue now and more a would be nice to have.

Log in to comment on this ticket.

Metadata