"sources.changes" is not a well-known term

Bug #509791 reported by William Grant
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
Fix Released
Medium
Julian Edwards

Bug Description

The Launchpad term "changesfile" was recently replaced by "sources.changes", which is not a term I have ever heard before.

Perhaps "source.changes" was meant, but I don't think that it's a good term to use either.

Tags: lp-soyuz

Related branches

Revision history for this message
William Grant (wgrant) wrote :

Also, it appears to be used for binary changes files too.

Revision history for this message
Stuart Bishop (stub) wrote :

This change was Bug #253525, which landed in lp:~launchpad/devel r10193 in case reverting is desirable.

Revision history for this message
Julian Edwards (julian-edwards) wrote :

I'll fix it "properly" myself. I'll use "changes file" which makes the most sense to me and most people, and works for binaries.

Changed in soyuz:
status: New → Triaged
importance: Undecided → Medium
assignee: nobody → Julian Edwards (julian-edwards)
milestone: none → 10.01
Revision history for this message
Jamal Fanaian (jamalta) wrote :

Well, I apologize that you feel so against this change. I had discussed it with a team member before I implemented the change, and then had a different team member approve the changes in my MP.

Julian, if you haven't already made the changes, I can quickly do it as I already have all the places in the templates and tests that this is referenced, as I made the change from changesfile to sources.changes just a few days ago. Let me know, I could have it fixed by lunch time EST.

Revision history for this message
Julian Edwards (julian-edwards) wrote : Re: [Bug 509791] Re: "sources.changes" is not a well-known term

Right, sorry, the person who said it was ok wasn't a Soyuz expert. However,
having just reviewed your branch, thanks very much for fixing it already!

Changed in soyuz:
status: Triaged → Fix Committed
Changed in soyuz:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.