Re: [sage-devel] Re: Git repository should have Sage versions as branches not tags

On Tue, Jul 19, 2016 at 10:08 PM, Robert Bradshaw wrote: > I was running a small script on trac.sagemath.org:12000 that was > listening for github pull requests and comments (via github webhooks) > and publishing them to trac (via the trac scripts shipped with Sage).

Re: [sage-devel] Re: Git repository should have Sage versions as branches not tags

I was running a small script on trac.sagemath.org:12000 that was listening for github pull requests and comments (via github webhooks) and publishing them to trac (via the trac scripts shipped with Sage). Nothing too fancy, but I can't find the code for it at the moment (but it's probably still

[sage-devel] Re: Git repository should have Sage versions as branches not tags

Samuel, there are a couple pull requests from the middle of 2015 that never became Trac tickets. The bot appears to have stopped creating tickets before then. There are open pull requests from the end of 2014 that became part of Sage 6.4. The bot does not appear to close pull requests on

Re: [sage-devel] Re: Git repository should have Sage versions as branches not tags

On Mon, Jul 18, 2016 at 12:46 PM, Thierry wrote: > Hi, > > On Mon, Jul 18, 2016 at 12:17:48PM +0200, Erik Bray wrote: > [...] >> Additionally, I think we should allow issues (without code) to be >> posted on GitHub, and have an easy way to convert a GitHub issue

Re: [sage-devel] Re: Git repository should have Sage versions as branches not tags

Hi, On Mon, Jul 18, 2016 at 12:17:48PM +0200, Erik Bray wrote: [...] > Additionally, I think we should allow issues (without code) to be > posted on GitHub, and have an easy way to convert a GitHub issue to a > Trac ticket. I don't think it should be done for all issues, but > rather use GitHub

Re: [sage-devel] Re: Git repository should have Sage versions as branches not tags

On Mon, Jul 18, 2016 at 10:12 AM, Samuel Lelievre wrote: > There is a bot (called sageb0t) that turns pull requests on GitHub into trac > tickets. > > It might be that the bot also closes pull requests when the corresponding > tickets > have been closed on trac and a

[sage-devel] Re: Git repository should have Sage versions as branches not tags

There is a bot (called sageb0t) that turns pull requests on GitHub into trac tickets. It might be that the bot also closes pull requests when the corresponding tickets have been closed on trac and a new public release of Sage happens (github pull requests are typically against the master

[sage-devel] Re: Git repository should have Sage versions as branches not tags

Don't know, possibly nobody On Sunday, July 17, 2016 at 11:06:37 PM UTC+2, Paul Masson wrote: > > Thanks. > > Another question: who closes Issues and Pull Requests on Github that have > been marked ready for closure? > > On Sunday, July 17, 2016 at 1:56:38 AM UTC-7, Volker Braun wrote: >> >>

[sage-devel] Re: Git repository should have Sage versions as branches not tags

Thanks. Another question: who closes Issues and Pull Requests on Github that have been marked ready for closure? On Sunday, July 17, 2016 at 1:56:38 AM UTC-7, Volker Braun wrote: > > done > > On Saturday, July 16, 2016 at 11:19:21 PM UTC+2, Paul Masson wrote: >> >> The mirror actually has three

[sage-devel] Re: Git repository should have Sage versions as branches not tags

done On Saturday, July 16, 2016 at 11:19:21 PM UTC+2, Paul Masson wrote: > > The mirror actually has three branches. This one hasn't been touched in > over a year: > > https://github.com/sagemath/sage/tree/module-list-cleanup > > Shouldn't it be removed at some point? > > On Wednesday, July 13,

[sage-devel] Re: Git repository should have Sage versions as branches not tags

The mirror actually has three branches. This one hasn't been touched in over a year: https://github.com/sagemath/sage/tree/module-list-cleanup Shouldn't it be removed at some point? On Wednesday, July 13, 2016 at 6:53:21 PM UTC-7, John Phamlore wrote: > > The mirror at > >

[sage-devel] Re: Git repository should have Sage versions as branches not tags

Checking out a branch or a tag should be pretty much the same. The only potential pitfall is that you need to quote numbers in yaml, otherwise they are interpreted as numbers. So change branch: develop into e.g. branch: '7.2' On Thursday, July 14, 2016 at 3:53:21 AM UTC+2, John Phamlore

[sage-devel] Re: Git repository should have Sage versions as branches not tags

> > However, editing sage.yaml of binary-pkg > > https://github.com/sagemath/binary-pkg > > does not work for tags. > Hmm, somehow I was able to come up with something, though I may be remembering wrong ... anyway, git definitely (so far as I can tell) would discourage a version release being