On Mon, Oct 8, 2012 at 9:36 PM, Aaron Meurer <asmeu...@gmail.com> wrote: > On Mon, Oct 8, 2012 at 2:42 PM, Ondřej Čertík <ondrej.cer...@gmail.com> wrote: >> On Mon, Oct 8, 2012 at 11:58 AM, Aaron Meurer <asmeu...@gmail.com> wrote: >>> On Mon, Oct 8, 2012 at 12:25 PM, Ondřej Čertík <ondrej.cer...@gmail.com> >>> wrote: >>>> On Sun, Oct 7, 2012 at 8:53 PM, Aaron Meurer <asmeu...@gmail.com> wrote: >>>> [...] >>>>> - We should release *at least* once a month. I think that if the >>>>> process is automated enough, that this will be very possible (as >>>>> opposed to the current situation, where the release branch lasts >>>>> longer than a month). In times of high activity, we can release more >>>>> often than that (e.g., after a big pull request is merged, we can >>>>> release). >>>> >>>> We should definitely automate it. I've had great experience with Vagrant, >>>> here are my scripts to automate the NumPy release: >>>> >>>> https://github.com/certik/numpy-vendor >>>> >>>> That among linux tgz even builds a binary for Windows. The advantage >>>> of Vagrant is that anyone can easily run it, both Mac or Linux and >>>> the environment is 100% the same. (Travis CI also uses Vagrant btw.) >>>> >>>> Aaron, are you able to run Vagrant on your Mac? Let me know if you >>>> are in favor of that, and I can write the initial release script using >>>> Vagrant, >>>> and then we keep improving it (all of us). >>> >>> It seems to work (at least I am able to install it). Is there a simple >>> way that I can test that it really works? >> >> Yes --- follow the instructions: >> >> https://github.com/certik/numpy-vendor#how-to-use >> >> it it starts doing something, then it works. It takes a few hours to >> actually build everything in Wine inside it, so you don't have to wait, >> just kill it with ctrl-C. >> >> You will need to have Fabric installed (https://github.com/fabric/fabric). >> >> That is the tool, that allows automatic manipulation of remote servers, >> in this case Vagrant VM. Later, we can extend our scripts to do some stuff >> on our Linode server or some other servers. > > I went ahead and did the whole process, and it worked just fine.
Cool, thanks for trying. Especially the wine thing is highly nontrivial, that took me days to figure out how to set it up. But once it's done, it works like a charm in Vagrant. So we can use this approach for our automation. > Well, half of the sites are our own (homepage, SymPy Live/Gamma, blog, > etc.). So we definitely should update those :) > > The rest, like Wikipedia or Freshmeat, I guess are not as important. > It helps for marketing purposes, but that's it. As for trying to get > it into the linux packaging repos, I'm not even going to bother. That > really should be someone else's job (if you want, we can add tasks for > it for GCI). Yes. Other people can help with updating pages, even our own. E.g. I can update our pages. Ondrej -- You received this message because you are subscribed to the Google Groups "sympy" group. To post to this group, send email to sympy@googlegroups.com. To unsubscribe from this group, send email to sympy+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/sympy?hl=en.
