Hi,
i suggest we move to the following git related procedure for doing
feature releases:
- merge from master to make sure all bugfixes are in
- release from feature, also tag the release
- merge feature into master which now becomes the new bugfix line
Currently for pytest-2.9 features was
On Sat, Feb 13, 2016 at 17:34 +, Bruno Oliveira wrote:
> On Sat, Feb 13, 2016 at 3:02 PM holger krekel wrote:
>
> > On Sat, Feb 13, 2016 at 16:46 +, Bruno Oliveira wrote:
> > > I'm under the impression that 2.9 is meant to be released this week.
> >
> > You mean this
On Sat, Feb 13, 2016 at 17:54 +, Bruno Oliveira wrote:
> Hi guys,
>
> I think the next step to complete the docs move to readthedocs is a server
> side configuration
> to redirect all requests from pytest.org to pytest.readthedocs.org... don't
> know anything about the subject, but a quick
On Sat, Feb 13, 2016 at 17:54 +, Bruno Oliveira wrote:
>
> I think the next step to complete the docs move to readthedocs is a server
> side configuration
> to redirect all requests from pytest.org to pytest.readthedocs.org... don't
> know anything about the subject, but a quick google
On Sat, Feb 13, 2016 at 3:54 PM holger krekel wrote:
> can you do the latter really? You'd have to transfer all html files
> because they have the generated link at the top of each page.
>
> Seems easier to transfer current master's _template/* and annouce/* onto
> the
>
Cool, thank youand Enjoy your weekend as well!
On February 13, 2016 8:04:48 PM GMT+01:00, Ronny Pfannschmidt
wrote:
>HI all,
>
>since the issue is my mistake to begin with, i just did a backport +
>upload of the changes and did put them into a branch at my repo
>next
On Sat, Feb 13, 2016 at 4:07 PM holger krekel wrote:
> Let's move back quickly, though, if there are any problems.
> So far i have not heart many complaints about pytest.org not working apart
> from the recent ssl hickup which should be automated now with letsencrypt.
>