I stopped developing for Sage largely because reviewers wanted me to use Mercurial queues. I gave up on trying to learn it. Is there a way to accomplish what Mercurial queues does without the learning curve?
asked Aug 18 '10timothyclemans
29 ● 3 ● 4
You don't have to use queues to contribute to Sage. As evidence, I didn't use queues at all until June 2010.
That said, I think it would be great if hg_sage were improved so that it could use queues without you having to know anything much about them. This would be an alternative answer to your question, if it existed. But it doesn't today.
By the way, I don't think queues are that hard. I used to think they were before I read the new tutorial at the developers guide page.
I don't know about the reviewers you worked with, but when I'm reviewing tickets, I only care about what kind of patches are posted -- I don't care how they were created. A clean diff, ticket number in the commit message, proper username...that's what I want.
Right now, probably not. But I did find that once I figured out queues, it was the most natural and easy way to work. Take a copy of Sage, qimport a patch, test it, pop and delete it -- and my copy of Sage is just like it started. Things get a bit more complicated with the sage-combinat stuff, since they have a huge queue and use guards and all that -- but you can ignore that stuff.
It sounds like much of your confusion would be cleared if you could sit down with someone and have them show you things -- or maybe a good chat on IRC with a shared screen session. Read the Mercurial book and ask questions. I think you can understand queues without too much trouble.
I've done a fair amount of Sage development and I still haven't learned queues. I do understand the ideas, and I see the advantages, so someday soon I will switch to them, but at the moment I am too lazy. You can just clone a copy of Sage, work in that, and if things get messed up clone another copy from the main branch. Cloning can be annoyingly slow but if you are multitasking its not that big a problem.
In summary: queues are good but not necessary.
posted Aug 19 '10mhampton
359 ● 2 ● 6 ● 15
For me, the hardest thing about queues was getting started after I'd already written some code and made some changes. I tried to be careful, follow the manual, and make backups, but I still lost work. When I made a fresh clone of sage and started queues before making any changes, things smoothed out a lot.
Asked: Aug 18 '10
Seen: 251 times
Last updated: Aug 19 '10
powered by ASKBOT version 0.7.22
Copyright Sage, 2010. Some rights reserved under creative commons license.