random thought - i do wonder if we should just publish a rss feed with the
releases
2016-09-14 18:33 GMT+02:00 holger krekel :
> On Wed, Sep 14, 2016 at 15:48 +0200, Florian Bruhin wrote:
> > Hey,
> >
> > * holger krekel [2016-09-14 13:58:18 +0200]:
> > > I am a bit concerned that people who tra
On Wed, Sep 14, 2016 at 15:48 +0200, Florian Bruhin wrote:
> Hey,
>
> * holger krekel [2016-09-14 13:58:18 +0200]:
> > I am a bit concerned that people who transfer repos to pytest-dev
> > think that it receives magic maintenance
>
> I read your sentence saying this does happen, and not that you
On Wed, Sep 14, 2016 at 8:58 AM holger krekel wrote:
> I am a bit concerned that people who transfer repos to pytest-dev think
> that it receives magic maintenance because this relevant section in the docs
>
>
> http://doc.pytest.org/en/latest/contributing.html#submitting-plugins-to-pytest-dev
>
anything that can run deploy scripts works
-- Ronny
2016-09-14 16:12 GMT+02:00 Sebastian Rahlf :
> Little word of caution: Not all plugins are on github/use git.
> Travis will only work with github projects afaik.
>
> Sebastian
>
> 2016-09-14 14:01 GMT+02:00 Ronny Pfannschmidt <
> opensou...@ron
Little word of caution: Not all plugins are on github/use git.
Travis will only work with github projects afaik.
Sebastian
2016-09-14 14:01 GMT+02:00 Ronny Pfannschmidt <
[email protected]>:
> sounds good to me,
>
> can we up the release automation requirements,
> so git tag + trav
Hey,
* holger krekel [2016-09-14 13:58:18 +0200]:
> I am a bit concerned that people who transfer repos to pytest-dev
> think that it receives magic maintenance
I read your sentence saying this does happen, and not that you're
concerned that it could happen, right?
If so, what makes you think t
On Wed, Sep 14, 2016 at 14:01 +0200, Ronny Pfannschmidt wrote:
> sounds good to me,
>
> can we up the release automation requirements,
> so git tag + travis deploys can be used for releasing?
FWIW i remain -0 on tag-triggers-release workflows.
holger
> best, Ronny
>
> On 14.09.2016 13:58, holg
another point, we might want to introduce an pytest-attic org
and move unattended pytest-dev repos there based on primary
maintainership going away
-- Ronny
On 14.09.2016 13:58, holger krekel wrote:
> I am a bit concerned that people who transfer repos to pytest-dev think that
> it receives mag
Ok.
On Wed, Sep 14, 2016 at 2:56 PM Bruno Oliveira wrote:
> I think the move is complete, let me know if you have any problems.
>
> Cheers,
>
> On Wed, Sep 14, 2016 at 8:13 AM Bruno Oliveira
> wrote:
>
>> Vital,
>>
>> The steps are detailed here:
>>
>>
>> https://github.com/pytest-dev/pytest/bl
sounds good to me,
can we up the release automation requirements,
so git tag + travis deploys can be used for releasing?
best, Ronny
On 14.09.2016 13:58, holger krekel wrote:
> I am a bit concerned that people who transfer repos to pytest-dev think that
> it receives magic maintenance because t
I am a bit concerned that people who transfer repos to pytest-dev think that it
receives magic maintenance because this relevant section in the docs
http://doc.pytest.org/en/latest/contributing.html#submitting-plugins-to-pytest-dev
is not very explicit about it, even says "sharing some of the m
I think the move is complete, let me know if you have any problems.
Cheers,
On Wed, Sep 14, 2016 at 8:13 AM Bruno Oliveira wrote:
> Vital,
>
> The steps are detailed here:
>
>
> https://github.com/pytest-dev/pytest/blob/master/CONTRIBUTING.rst#submitting-plugins-to-pytest-dev
>
> I already crea
Vital,
The steps are detailed here:
https://github.com/pytest-dev/pytest/blob/master/CONTRIBUTING.rst#submitting-plugins-to-pytest-dev
I already created the teams, feel free to transfer ownership of the
repository to me.
Cheers
On Tue, Sep 13, 2016 at 1:49 PM Vital Kudzelka
wrote:
> I prefer
13 matches
Mail list logo
