Closed Bug 1524961 Opened 1 year ago Closed 1 year ago

[mozlog] Update MPL to latest version


(Testing :: Mozbase, enhancement, P3)

Version 3


(firefox68 fixed)

Tracking Status
firefox68 --- fixed


(Reporter: raphael, Assigned: pgadige__)



(4 files)

Currently mozlog is released under the MPL 1.1. Update the license to MPL 2.0 and publish a new release.

Priority: -- → P3

(In reply to Raphael Pierzina [:raphael] UTC+01:00 from comment #0)

I'm working on fixing this issue.

Currently mozlog is released under the MPL 1.1. Update the license to MPL 2.0 and publish a new release.

I suppose the license should be updated on mozlog's PyPI page as MPL 2.0
So I think I should modify its file located at to reflect the new license.

I found a similar issue #1286557 was raised sometime ago. May I mark that one as duplicate of the current one?

Thank you!

Flags: needinfo?(rpierzina)

Updated the license for mozlog library by setting the new license number, MPL 2.0, in mozlog's file.

This patch updates mozlog license to MPL 2.0

Raphael and Geoff, I wonder if either of you could please review my patch and provide feedback.

Thank you!

Hey :pooja! Thank you for submitting a patch for this bug. I will have a look tomorrow!

Flags: needinfo?(rpierzina)
Assignee: nobody → poojagadige

Thank you, :raphael , for reviewing the change.

I've resolved the review comments as needed.

Please let me know if there is something amiss.

It's kinda strange that a new Differential Revision was created when I ran moz-phab after rewriting the commit message using hg amend -m.

Phabricator works by leaving an identifier in the commit message. When you run hg amend -m you overwrite the commit message with the new one, losing the identifier in the process. Then moz-phab doesn't see any revision to update so creates a new one.

In the future just use hg amend or hg commit --amend if you need to change the message.

Pushed by
Update mozlog's license to MPL 2.0. r=raphael
Closed: 1 year ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla68
You need to log in before you can comment on or make changes to this bug.