Well this time was a bit extreme since Apple screwed us over at the last
minute, causing extra delays. I also just got back from vacation. If it
would have been up to me I'd have made the release before leaving, but then
people complained that this is too fast.
What would be nice if there were a patchbot that does pdf doc builds, these
tend to be broken quite often.
Merging 200 tickets is not a big deal imho. I also don't think that there
is a big risk of non-trivial merge conflicts, there are enough loc to
spread out those changesets...
On Monday, May 7, 2018 at 4:55:24 PM UTC+2, Jeroen Demeyer wrote:
>
> (starting a new thread for the discussion about the current very slow
> pace of merging tickets)
>
> On 2018-05-07 16:28, Erik Bray wrote:
> > If it's not clear, shall I write up some more formal documentation for
> > my proposed process?
>
> To be honest, I think it's not very meaningful to do that without
> consulting the release manager. I mean, you can write up all the
> documentation that you want; in the end, it's the release manager who
> decides what happens.
>
> I do agree that there is a problem though. We are close to 200
> positively reviewed tickets just sitting there. And my fear of conflicts
> is certainly holding me back to do further Sage development for the
> moment (luckily, I had PEP 575 and the Cernay workshop to keep myself
> busy).
>
> So Volker, what's your opinion on this?
>
--
You received this message because you are subscribed to the Google Groups
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.
