Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Mark these pkgdb examples as Legacy #146

Merged
merged 2 commits into from Sep 22, 2014
Merged

Conversation

ralphbean
Copy link
Contributor

This needs scrutiny from @pypingou and @tyll.

By marking these tests as Legacy, they will no longer show up in the
docs at http://fedora-fedmsg.readthedocs.org/en/latest/topics.html

In fedora-infra/fedmsg#255, @tyll mentioned that some pkgdb1 messages
still appeared in the docs even though they are not being broadcast
anymore. I did my best to check that the topics of these messages that
I've marked do not actually appear in the pkgdb2 source, but I'd be much
more comfortable merging this if someone more familiar with the source
could look over them.

If merged, this fixes fedora-infra/fedmsg#255.

This needs scrutiny from @pypingou and @tyll.

By marking these tests as ``Legacy``, they will no longer show up in the
docs at http://fedora-fedmsg.readthedocs.org/en/latest/topics.html

In fedora-infra/fedmsg#255, @tyll mentioned that some pkgdb1 messages
still appeared in the docs even though they are not being broadcast
anymore.  I did my best to check that the topics of these messages that
I've marked do not actually appear in the pkgdb2 source, but I'd be much
more comfortable merging this if someone more familiar with the source
could look over them.

If merged, this fixes fedora-infra/fedmsg#255.
@@ -1241,7 +1241,7 @@ class TestPkgdbDeleteAcl(Base):
}


class TestPkgdbBranchRequest(Base):
class LegacyTestPkgdbBranchRequest(Base):
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This one is needed by the admin_action branch, you just have code here that's not yet live :) (for once ^^)

@pypingou
Copy link
Member

I'll have to check for the first two, the last two are definitevely of interest.

As discussed in #146, they correspond to messages that are a part of the
pkgdb ``admin_action`` branch.
@ralphbean
Copy link
Contributor Author

OK, 13661ec should fix that. I'll wait on another review from @pypingou or @tyll before merging.

@@ -443,7 +443,7 @@ class TestLegacyPkgdbPackageRetire(Base):
}


class TestPkgdbUserRemove(Base):
class LegacyTestPkgdbUserRemove(Base):
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Using git grep -i remove I see nothing involving fedmsg, so that one is safe for sure

@pypingou
Copy link
Member

👍 for me, looks safe

ralphbean added a commit that referenced this pull request Sep 22, 2014
@ralphbean ralphbean merged commit d2a61a1 into develop Sep 22, 2014
@ralphbean ralphbean deleted the feature/pkgdb-legacy branch September 22, 2014 17:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

update message topics due to pkgdb update
2 participants