On Mon, Jan 12, 2015 at 3:58 PM, Johannes Ring <[email protected]> wrote: > On Mon, Jan 12, 2015 at 2:53 PM, Johannes Ring <[email protected]> wrote: >> On Mon, Jan 12, 2015 at 11:02 AM, Benjamin Kehlet <[email protected]> wrote: >>> >>> >>> Den mandag 12. januar 2015 skrev Garth N. Wells <[email protected]> følgende: >>>> >>>> >>>> >>>> On Mon, 12 Jan, 2015 at 9:34 AM, Johannes Ring <[email protected]> wrote: >>>>> >>>>> On Mon, Jan 12, 2015 at 10:31 AM, Chris Richardson < [email protected]> >>>>> wrote: >>>>>> >>>>>> On 09/01/2015 15:56, Martin Sandve Alnæs wrote: >>>>>>> >>>>>>> >>>>>>> Will that be a beta? >>>>>>> >>>>>> >>>>>> >>>>>> I am going to suggest that Johannes builds the 1.5.0 release today (or >>>>>> as >>>>>> soon as he can fit it in his schedule) from the current master... >>>>>> >>>>>> Any objections, raise them now. Everyone has had plenty of time to do >>>>>> whatever they wanted to do for 1.5.0. >>>>>> >>>>>> I would call it a "major" release, and that if there are any serious >>>>>> bugs, >>>>>> we can make a "minor" release 1.5.1 to fix them. >>>>> >>>>> >>>>> I agree and I am ready to make the release today. >>>> >>>> >>>> Benjamin may be working on the last remaining issue targeted for 1.5: >>>> >>>> >>>> https://bitbucket.org/fenics-project/dolfin/issues?milestone=1.5&status=open&status=new >>> >>> >>> Yes, I will push a fix very soon. >> >> I have merged the fix from Benjamin now and will make the release if >> the buildbot stays green. > > The buildbot is still green (except for precise-i386 which has been > timing out for a long time) so I will start making the release. Can > someone prepare the release notes for the web page?
The 1.5 tarballs for DOLFIN, FFC, FIAT, Instant, UFL and uflacs have been generated. What about mshr? Is this ready for a 1.5 release? The documentation has also been generated for 1.5 and I have started working on the binary packages. They will probably be available tomorrow. We also need to reset the next branches and delete all merged branches. How do we reset the next branch? Johannes
_______________________________________________ fenics mailing list [email protected] http://fenicsproject.org/mailman/listinfo/fenics
