troposphere needs to be changed to enforce the following constraint:
"For any package version N@V with earliestCompatibleVersion E, if
N@E is a published version, then its earliestCompatibleVersion is
also E."
In this way, earliestCompatibleVersion partitions the set of versions of
a package into compatibility classes. There's no need to do comparisons
on ECVs; instead, you just can check to see if two versions have the
same ECV.
This makes some of the ECV logic simpler.
It should not longer be allowed to depend on a version that does not
exist (although this should really be an immediate error instead of an
unsatisfiable constraint like it is with this commit).
it is way too hard to get a non-portable package to work both from
uniload (which can't depend on non-core packages) and with meteor deploy
from checkout on mac (which basically requires a non-core package to
have the non-portability in it)
1. Now it matches `logging:test`, not `logging:tests`.
2. Now it is okay with server-side source maps, by matching
`/packages/logging/foo.js` in addition to `/packages/logging.js`.
This reverts commit 7e519e11b7.
This commit added a test that upgraded from srp to bcrypt via
changePassword for a user with only an email address, in addition to the
test that existed for a user with a username. Having two such tests is
now silly because Meteor.changePassword no longer has different code
paths for email/username users.
DomRange now never removes elements except through the removeElement UI hook. If you write a hook that prevents removal, teardown still happens (e.g. templates stop updating).
This code also provides the basis for stopping updates to part of the DOM by triggering teardown without removal.
Before, DomBackend.removeElement would both trigger teardown and actually deparent the element. Now we have DomBackend.tearDownElement, which just triggers the jQuery teardown (which in turn triggers finalization of DomRanges that have been inserted in the DOM tree).
The flag to {node,members,range}Removed is now named “alreadyTornDown” and documented. Its purpose is to prevent redundant teardown walks through the DOM.
