On Feb 21, 2:27 am, Rob Beezer <goo...@beezer.cotse.net> wrote: > I'm inclined to update the "Walking Through the Development Process" > section of the Developer Guide. > > I've had some feedback (in-person) and have seen a few thoughtful > comments in various places in sage-devel. Other than mentioning new > features (like "hg qpush --move" (!) and the patchbot) and technical > details, I'd like to split out the notion of clones being "easier" > than queues. What I am hearing is that both have their place > (including some very experienced developers who use clones for big > projects), so I would like to put each on an equal footing and try to > give some clear "upsides" and "downsides" to their use. > > I'd also like to try to streamline the walk-through to an absolute > bare minimum of the essentials to get started reviewing or > contributing, with a greater reliance on pointers to sections of the > guide (which may be newly-formed from the existing walk-through). > > So this is a call for input. I'd especially love to hear reactions/ > suggestions from folks who have used this section as a way to get > started with Sage development.
I used the guides for getting to know the development process. I'm still new, so there are probably better working processes than what I do, and of course, this will be reflected in my opinons. > > * Pros/cons of clones/queues? I have some good ideas here, but weigh- > in if you like. I'm not asking which *you* prefer, but instead > *reasons* to prefer one over the other. I'm _only_ using queues at the moment. As far as I can see, clones are neat if you have "projects" of patches. However, the beginner will not usually have this but only a few scattered fixes here and there and patches for review, with none or few dependencies between them. For this, I think queues are much faster and lightweight. I began with the clones just like the guide said, but found it tiresome and switched to the queues as soon as I got to that part of the guide. Also, clones are time consuming in the beginning when you are anxious to just get started. I definitely don't think that they should be part of the beginning of this walk-through. I would use clones if I reviewed as many patches as I should; then I would have a clone for my work (and patches that I need), and another clone for the non-dependent set of patches I was currently reviewing. However, I always have a clean, completely separate install of the last stable release of Sage. I can't remember if that is mentioned in the guide, but I find this helpful (and necessary) in a number of ways. This only have the patches applied which I really need. > > * Development styles/practices/strategies not mentioned in the > Developer Guide? I more or less already described my style though it is not very deep. I think it would be immensely inspirational with a link to a page where several of the veterans had described their own style (in a lot of detail), possibly with links to various of their custom build/patch/ etc. scripts. Regards, Johan -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
