On 29. 01. 19 20:31, Stephen John Smoogen wrote:
This is like the 4th system wide change this release which is coming in as a
Self-Contained. Each time the developer thinks it is self-contained because it
is just one little thing, but on regards it turns into being a system-wide
change. However because the two deadlines are one after the other, it means that
this change is pushed out another 6 months where the 3-4 weeks between
System-Wide and Self-Contained doesn't seem very long. Can we either:
1) Move System-Wide and Self-Contained proposal deadlines to be the same date
and allow FESCO/etc determine if the proposal needs to be moved to SW or SC then?
2) Move Self-Contained deadline BEFORE System-Wide so that if it is really
System-Wide move it to the correct category?
3) Add a re-evaluate deadline after the first two? This allows us to get an idea
that "oh wait this is going to really mess things up and we need to push this
out one release?" or other items
I'm starting a new thread about this so it is not buried in the YUM3 removal thread.
I don't think 2 brings us any benefit over 1.
I understand the need of soon deadline for changes needing the mass rebuild.
However I guess changes not needing it might share a deadline, so we are able to
"upgrade" a Self Contained change proposal to System Wide without postponing to
the next Fedora release.
Before we do any changes, what is the actual reasoning for two deadlines?
Is it the assumption that System Wide changes need more time? That is not always
correct.
--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
