removed assertion about ancestor revision.
log this as a warning, and let it proceed.
ref #829

--HG--
branch : beta
extra : amend_source : b60fc41f89722c324a1e7c451bed80030b5df003
invalidation: merge .invalidate and .set_valid as .test_and_set_valid

This simplifies the internal API and avoids leaking CacheInvalidation instances
and cache keys.

--HG--
branch : beta
extra : source : fe9c99ee2d1e0042288c76208e7ed576c278f2cf
invalidate: encapsulate how key is generated from repo_name and kind

--HG--
branch : beta
extra : source : 2bdc6d81f5a22295cff452d6054956a6db51857e
invalidation: don't create CacheInvalidation records on startup

Creating the records early gave an advantage before lightweight was introduced.
With lightweight it is no longer necessary.

The records will be created on demand anyway and there is no reason to create and
maintain them before they are used.

--HG--
branch : beta
extra : source : a941f32fc5a63ee0d7f08944f2ea9e5bebc876c7
extra : amend_source : 51d17b42d3d7518b40b7d145b784a81c671d16be
fixed some issues with paginators on chrome, and made them  look nicer

--HG--
branch : beta
Unified the paginators for pylons and YUI.
- YUI based paginators now behave more like the ones generated with pylons
- introduced new custom pylons paginator for customizations needed to unify both

--HG--
branch : beta
cleanup code

--HG--
branch : beta
added initial_repo_scan flag for controll if repo scaning should be performed on every startup.
There's always paster repo-scan or repo scann triggered from admin pannel

--HG--
branch : beta
html: move "Submit a bug" to make it more clear that it is for RhodeCode, not the repo

RhodeCode _could_ contain a bug tracker and this link _could_ be for filing
bugs for the hosted projects.

Moving the link to the RhodeCode info makes it more clear that it is for
RhodeCode bugs.

The server instance is however something local, not directly related to the
upstream.

--HG--
branch : beta
emails: try to improve wording and layout - 1st iteration

--HG--
branch : beta
emailing: log failing emailing as an error

TODO: The failure should be reported back to the user (or the admins). The
system should not silently not send any emails to the targeted recipients.

Even better: it should inform the user whenever emails was (scheduled to be)
sent - and to whom.

--HG--
branch : beta
summary: don't link from 'Fork of' text - only repo name should link

--HG--
branch : beta
It's better to use Exception here than assertion. It plays better with the exception handling software like sentry or errormator

--HG--
branch : beta
extra : rebase_source : 92b201ebeb0cc4600a7c9b3dff8d8667c56bf3fc
make sure we hide the spans

--HG--
branch : beta
create a list out of generator.
Generator gets exausted during later executions, and because it's used several times
it causes errors

--HG--
branch : beta
Added separate default permission for external_auth account
activation. This flag allows users to define separate option of how
activation of external_accounts should be performed.

--HG--
branch : beta
fixed tests

--HG--
branch : beta
UserGroup on UserGroup permissions implementation.
- user group can have another usergroup assigned
- it's impossible to assign usergroup on the same usergroup

--HG--
branch : beta
managing users groups enforce permissions checks.
User needs at least a read permissions on usergroup to be able
to assign it somewhere.

--HG--
branch : beta
show link to usergroups if we have a create usergroup permission

--HG--
branch : beta