Closed Bug 781105 Opened 12 years ago Closed 12 years ago

Bump versions of manifestdestiny=0.5.5 and mozrunner=5.9 and release on PyPI

Categories

(Testing :: Mozbase, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: whimboo, Assigned: whimboo)

References

Details

Attachments

(1 file)

With the fix on bug 771030 we want to release a new version of the manifestdestiny package. This bug covers the release process.
Attachment #649991 - Flags: review?(jhammel)
Blocks: 771029
Shall we wait for bug 781239?
(In reply to Henrik Skupin (:whimboo) from comment #2)
> Shall we wait for bug 781239?

Yeah, i'd prefer that.  Didn't even realize that was b0rken
I don't think we want to or need to bump mozprofile and its downstream, mozrunner, for this bug.  This adds a feature and doesn't change the API so ManifestDestiny >= 0.5.4
 should continue to be fine
Because of bug 771029 we would also have to bump mozrunner. So excluding mozprofile is enough?
No longer blocks: 771029
Depends on: 780841, 771029
Summary: Bump version of manifestdestiny package to 0.5.5 and release on PyPI → Bump versions of manifestdestiny=0.5.5 and mozrunner=5.9 and release on PyPI
Blocks: 771029
No longer depends on: 771029
Depends on: 781239
Blocks: 781473
(In reply to Henrik Skupin (:whimboo) from comment #5)
> Because of bug 771029 we would also have to bump mozrunner. So excluding
> mozprofile is enough?

Works for me
(In reply to Jeff Hammel [:jhammel] from comment #6)
> > Because of bug 771029 we would also have to bump mozrunner. So excluding
> > mozprofile is enough?
> 
> Works for me

My only concern here is that things like that will make it harder to run regression tests. Even non API-Changes can cause misbehavior. But that's another topic. So for now I will update my patch and kill the bump of mozprofile.
Andrew, if you step in earlier as Jeff and can review my patch I would appreciate it. Would like to land it to be able to continue with the Mozmill blockers. Thanks.
Comment on attachment 649991 [details]
Pointer to Github pull request: https://github.com/mozilla/mozbase/pull/29

Looks good.
Attachment #649991 - Flags: review?(jhammel) → review+
https://github.com/mozilla/mozbase/commit/d22b344a90f27a4a917d26658c0f09cefc6f8e38

Tags:
https://github.com/mozilla/mozbase/tree/mozrunner-5.9
https://github.com/mozilla/mozbase/tree/ManifestDestiny-0.5.5

PyPI:

Submitting dist/ManifestDestiny-0.5.5.tar.gz to http://pypi.python.org/pypi
Server response (200): OK

Submitting dist/mozrunner-5.9.tar.gz to http://pypi.python.org/pypi
Server response (200): OK
Status: ASSIGNED → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
FYI for the future, version bumping does not need an issue filed or review:

https://wiki.mozilla.org/Auto-tools/Projects/MozBase#Review_Policy

You are of course free to do this if you want to.
It was also an update of the readme. And as talked with Jeff he wants to have a bug filed for tracking purposes.
The page also states that documentation does not require a review.  I do want tracking bugs for version bumps (and probably substantive documentation changes).  However, these changes do not require review of the resulting patches.  As Will says though, feel free to ask for review if you want it.
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: