Closed Bug 805190 Opened 7 years ago Closed 7 years ago

document new procedure for mozbase mirroring and versioning

Categories

(Testing :: Mozbase, defect)

defect
Not set

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: k0scist, Assigned: k0scist)

References

Details

(Whiteboard: [leave open])

Attachments

(1 file)

We had a meeting today to figure out what was working and not working
about mozbase versioning and we decided a few things.  From
https://etherpad.mozilla.org/mozbase-versioning

"""
when/what/how to mirror to m-c
- currently we mirror all of mozbase; this makes it (effectively)
impossible to run the same version in-tree as out of tree
- alternatives: mirror specific versions (and bump version on
mirroring to m-c)
-- do we always merge on version bump?
-- do we need a manifest?
DECISION: We will start versioning before any merges of them to
m-c. Only the package(s) in question will be merged to m-c.
pegging versions:
- currently we are inconsistent in specifying versions
- should we peg to exact versions?
- internal to mozbase vs external?
DECISION: We will use '>=' for internal deps
how should we ensure that we know what all depends on what version?
- http://k0s.org/mozilla/mozbase/dependencies.html is a strawman (not
very dynamic)
- could be a general tool
"""

In short, we want to start mirroring packages -> m-c versus whole
repository snapshots.  (I will also write some tools to make this
easier that probably will not live in the mozbase or m-c repo to start
off.) We should also start peggin >= versions.  Both of these can be
done with eventual concurrency (that is, going forward) without
penalty ABICT.

This should all be written up as well as the reasons why this was
decided on and the advantages and disadvantages of doing this.  I'd
also like to write a blog post about mozbave development methodologies
once this is done.
Assignee: nobody → jhammel
http://mxr.mozilla.org/mozilla-central/source/testing/mozbase/generate_diff.py should be either deleted or updated to this end as well
Noticed today that we're tagging based on directory name vs the package name, e.g. https://github.com/mozilla/mozbase/blob/master/mozinstall/setup.py#L20 vs https://github.com/mozilla/mozbase/zipball/mozinstall-1.1 . We should probably figure out which one we want (obviously there is a 1:1 mapping here; in some ways the directory names would be easier, i.e. this bug)
Summary: document new procedure for mozbase mirrorin and versioning → document new procedure for mozbase mirroring and versioning
(In reply to Jeff Hammel [:jhammel] from comment #2)
> Noticed today that we're tagging based on directory name vs the package
> name, e.g.
> https://github.com/mozilla/mozbase/blob/master/mozinstall/setup.py#L20 vs
> https://github.com/mozilla/mozbase/zipball/mozinstall-1.1 . We should
> probably figure out which one we want (obviously there is a 1:1 mapping
> here; in some ways the directory names would be easier, i.e. this bug)

noted: bug 805880 ; it would be nice to figure that out ahead of this bug, as whatever lives in m-c will be dependent on this solution
See Also: → 805880
This now works a bit differently...let's make sure we're okay with this
Attachment #675846 - Flags: review?(wlachance)
Comment on attachment 675846 [details] [diff] [review]
update generate_diff.py file

This looks about right to me. If you've tested it, go ahead and commit!
Attachment #675846 - Flags: review?(wlachance) → review+
I've tested it about as well as I can locally. Seems to work.
(In reply to William Lachance (:wlach) from comment #5)
> Comment on attachment 675846 [details] [diff] [review]
> update generate_diff.py file
> 
> This looks about right to me. If you've tested it, go ahead and commit!

pushed: https://hg.mozilla.org/integration/mozilla-inbound/rev/e2c6b346d1df
Whiteboard: [leave open]
I'm going to call this "done for now", though if there's anything big I've missed please reopen and poke.  I'm sure there will be follow-ups.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.