[pytest-dev] release process feature/master merge

holger krekel holger at merlinux.eu
Sat Feb 13 12:54:34 EST 2016

On Sat, Feb 13, 2016 at 17:34 +0000, Bruno Oliveira wrote:
> On Sat, Feb 13, 2016 at 3:02 PM holger krekel <holger at merlinux.eu> wrote:
> > On Sat, Feb 13, 2016 at 16:46 +0000, Bruno Oliveira wrote:
> > > I'm under the impression that 2.9 is meant to be released this week.
> >
> > You mean this weekend or the coming couple of days?
> >
> I was thinking the coming couple of days (say Thursday)... what do you
> think Ronny?
> Hmmm on the other hand it would be nice IMO to make a release candidate and
> ask users to test it to get some field testing, so this might push the
> release further in the week...
> I guess it's ok although if it drags any further i'd very much
> > appreciate if someone could "backport" the doc changes such that we can
> > push it to pytest.org rather sooner -- after all it's about
> > getting some of the ~37K monthly users to the site to donate.
> >
> Backporting the doc changes would mean cherry-picking the changes in a
> branch over the 2.8.7 tag and making a 2.8.8 release... if 2.9.0 is not
> released next week we can go with this plan.
> Another option would be to copy just the relevant html files to the live
> server... but that feels hackish. On the other hand is quick to do.

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
2.8.7 tag in a new branch and generate and push docs from there.
Could you do that?  With a bit of git-fu i suspect it's just a couple
of minutes ... not for me, though, and i have two children to care 
for currently :)


> Bruno.

about me:    http://holgerkrekel.net/about-me/
contracting: http://merlinux.eu

More information about the pytest-dev mailing list