2018-05-07 17:08 GMT+02:00 Erik Bray:
>
> On Mon, May 7, 2018 at 4:55 PM, Jeroen Demeyer:
> > (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.
>
> Sure, that goes without saying. That doesn't mean it isn't a good
> idea to document an idea more carefully for the review of all those
> involved. Such documentation would only be an initial draft.
> Unfortunately Sage development does not have a PEP-like process in any
> formal sense either. Maybe it should.
There once was a list of Sage enhancement proposals or "SEP"s
https://wiki.sagemath.org/devel/SEP
Most of the pages it links to have been archived, you need to append
?action=info
to their urls to get the history of each and see what they were about.
Samuel
--
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.
