On Tue, Aug 21, 2018 at 5:05 PM William Stein <wst...@gmail.com> wrote: > > On Tue, Aug 21, 2018 at 1:43 AM, Erik Bray <erik.m.b...@gmail.com> wrote: > > > Some of you may remember this is not a first for Sage either: some > > time ago there was a similar experiment done with GitHub, but it fell > > unmaintained. If anyone has any lessons learned from that time, > > please add them. > > I think Robert Bradshaw set all of that up during a Sage Days, then > went back to his normal fulltime job and > basically didn't look at it again. So it was unmaintained just due to > lack of time/focus, and not some deeper > issue.
That was my impression as well, but I still wondered if anyone had any particular experiences from that that they remembered. In particular I'm of course interested in Volker's opinion, as release manager. My "bot" has gone through a few iterations, and the current version is in fact actually just a Trac plugin, so it integrates closely with our existing Trac server and git repository. I've tried to make it explicitly compatible with his current process and to not get in the way of anything. Of course, if adjustments are needed in practice, they will be easy for me to make. > > What does everyone think? Is there anyone opposed to going ahead and > > opening up merge requests? > > > > +1. Thanks!!! > > -- > William (http://wstein.org) -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
