#3539 Change: TagLib2
Closed: Accepted by sgallagh. Opened by alking.

Update the taglib package from 1.13 to 2.x (2.1.1 as of the time of writing), which is an ABI and API break, and rebuild or port all dependents to the new version.

Owners, do not implement this work until the FESCo vote has explicitly ended.
The Fedora Program Manager will create a tracking bug in Bugzilla for this Change, which is your indication to proceed. See the FESCo ticket policy and the Changes policy for more information.

REMINDER: This ticket is for FESCo members to vote on the proposal. Further discussion should happen in the Discourse discussion linked above. Additional discussion may happen on the Fedora Devel mailing list.


Metadata Update from @ngompa:
- Issue assigned to yselkowitz

+1

@yselkowitz you might want to explicitly mention that you are a provenpackager, and can do all the rebuilds yourself, otherwise some people might wonder why this is self-contained.

Thank you all. This ticket has been open for 8 days with a vote of (+6, 0, -0). Shouldn't this be approved and a BZ opened so implementation can begin?

Yes, this is APPROVED (+6, 0, -0) after 7+ days.

And you do not need to wait for a tracking bug before starting to work on this. :)

Metadata Update from @decathorpe:
- Issue tagged with: pending announcement

After a week: APPROVED (+6, 0, 0)

And you do not need to wait for a tracking bug before starting to work on this. :)

Depends on how you read https://docs.fedoraproject.org/en-US/program_management/changes_policy/ I suppose?

"Do not implement your proposal until the FESCo vote has ended. When the Change Wrangler (FOA) creates a tracking bug for your issue, that is your indication to proceed."

But I'll take your comment as permission to proceed. Thanks!

"indication" doesn't sound very strong in my book.

I think for quite a while we've treated formal approval as the point in time when you can start working on something.

We should probably clean that up and also make it explict that formal approval happens at the moment that 7 days have passed with the +3/-0, irrespective of whether a FESCo member has gone ahead and added the APPROVED comment.

Not that I have any say in the matter, but if I did, I would feel better about requiring the APPROVED comment (but not necessarily the BZ or update of the wiki page etc.) rather than allowing individuals (who may or may not be familiar with procedure) to "decide" this themselves.

Yeah, I agree with @yselkowitz here. The rules are complex enough that we have discussions about corner cases within FESCo all the time so opening this up for anyone to interpret if the threshold was met is not a great idea. We also have other channels of discussion (at least the meetings, but sometimes in some other channels too) and the decision on the status may need to take those into account.

I'd prefer to standarize on requiring the APPROVED comment, and put that explicitly in the FESCo voting rules and in the template that is used here. We should also add a note that it's OK to ping for somebody to check if the vote has ended.

OK, yeah I suppose I can see where that might get hairy...

I was mostly just trying to consider those cases where a FESCo member doesn't notice that a Change should have been approved six days earlier. But if we ask them to ping for confirmation, I think that would be fine.

Filed https://pagure.io/fesco/issue/3559 for the policy discussion. Other change owners are having similar questions, so this would be good to clarify (at least ad-hoc for now).

Metadata Update from @sgallagh:
- Issue close_status updated to: Accepted
- Issue status updated to: Closed (was: Open)

Metadata