On 21. 11. 18 12:05, Adam Samalik wrote:
On Wed, Nov 21, 2018 at 11:07 AM Miro Hrončok <mhroncok(a)redhat.com
On 21. 11. 18 9:46, Adam Samalik wrote:
> Hi all,
> I have a post  I'd like to publish at the Community Blog.
> It's is a post by Petr Hracek originally submitted to Fedora
> The editorial board has agreed it’s more community focused, and we
> thought that publishing it here would be a better fit. What do
> Before publishing it, we'd need to change the author to be Petr
Hi Adam, Petr. Would you like a quick review from a fellow Pythonista?
I think that would be really helpful!
If so, could you enable public preview or send me the text via a side
Sorry I thought that link was already public. This one should work:
>  "How to get upstream releases into PyPi and Fedora with
* Github is spelled GitHub (you are using both)
* PyPi is spelled PyPI (also mixing it)
a new git repository named mtf-release-bot which contains conf.yaml
file and the other secret files.
Where do I push this secret repo? Advise not to push it as public maybe?
# list of fedora branches bot should release on. Master is always
Maybe don't list near eol fedora as an example?
For meta-test-family case, the configuration file looks like:
Foooo, legacy Python projects should IMHO not by endorsed by Fedora like
this. Pick a Python 3 ready example? Add a notice that Python 3 support
is being work on (is it?)?
Releasing to PyPI requires to have the wheel package both for python
and python 3, therefore please install requirements.txt with both
versions of pip.
What requirements.txt? Where do I install it? How?
How to deploy release-bot
How to deploy **with** release-bot?
Also, at this part of the article, I have no clue what so ever what the
bot actually does.
I fail to understand what does "release in Fedora" mean.
Where do I run the bot? Why don't I use some kind of CI serveice that
deos this for me:
I push a git tag => it runs the test, makes a release on PyPI, makes a
release in Fedora (whatever that means).
Maybe describe better what the bot actually does. E.g. it is hooked to
GitHub issues and waits for some kind of instructions? What are those
instructions? What will the bot actually do when it follows those
instructions? Does the bot run on OpenShift as a service?