On 22 April 2013 22:32, R. Andrew Ohana <andrew.oh...@gmail.com> wrote: > When 5.9, 5.10, ... are out is up to Jeroen. > > My goal is to have everything reviewed by mid/late June, so assuming I meet > my goal then I expect a 6.0 release in the Augest-September time frame > (assuming about a month gestation period for releases).
Thanks. So up until August at least development (bug fixes etc) will still use hg. John > > > On Mon, Apr 22, 2013 at 2:14 PM, John Cremona <john.crem...@gmail.com> > wrote: >> >> Thanks for the detailed workplan, that is useful. Any ideas at all on >> when these releases (5.9, 5.10, 6.0) will be out? Perhaps that is not >> a fair question from someone not contributing to the transition -- >> sorry! >> >> John >> >> On 22 April 2013 20:41, R. Andrew Ohana <andrew.oh...@gmail.com> wrote: >> > I've been posting git releases in the sage-git mailing list, and once >> > #14330 >> > is merged I'll start posting the git releases to the sage-release >> > mailing >> > list. Otherwise, here is the status: >> > >> > Known issues: >> > -- sagenb is broken (will be fixed with sagenb-0.10.6 -- this is >> > #14330) >> > -- 2 doctest failures in the doctesting framework (needs the >> > development >> > scripts, which haven't been merged into the git repository yet) >> > >> > Other stuff needed: >> > -- development scripts (which were primarily written before there was >> > a >> > workable repo) need to be heavily tested, have docstrings and doctests >> > completed >> > -- documentation needs writing >> > -- patchbot git compatibly needs finishing (and trac integration) >> > >> > >> > And the current release plan: >> > >> > 5.9, 5.10, ... -- everything vital to transitioning to git is finalized >> > 5.X (last release) -- concurrent classic and new workflows, with some >> > scripts to help make mecurial patches for those working in the new >> > workflow >> > 6.0 -- release is managed using the new workflow (and scripts will be >> > around >> > to help move patches to the new workflow) >> > >> > The idea being that the second to last release in the 5.X series has all >> > known kinks worked out for the transition to git (that is to say, all >> > the >> > significant changes needed[1] for the transition are reviewed prior to >> > this >> > release), the last release in 5.X series would encourage mass usage >> > (maybe >> > with a sage days to educate on the new workflow), and the 6.X release >> > would >> > be developed solely on the new model. >> > >> > >> > Hopefully that helps get everyone up to date on the status on the git >> > transition who aren't following the dedicated mailing list. >> > >> > -- >> > Andrew >> > >> > -- >> > 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 http://groups.google.com/group/sage-devel?hl=en. >> > For more options, visit https://groups.google.com/groups/opt_out. >> > >> > >> >> -- >> 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 http://groups.google.com/group/sage-devel?hl=en. >> For more options, visit https://groups.google.com/groups/opt_out. >> >> > > > > -- > Andrew > > -- > 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 http://groups.google.com/group/sage-devel?hl=en. > For more options, visit https://groups.google.com/groups/opt_out. > > -- 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 http://groups.google.com/group/sage-devel?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
