Yes, I think mshr should be moved to https://bitbucket.org/fenics-project/.

I can do this next week together with Benjamin if there are no objections.

--
Anders


Tue Jan 13 2015 at 11:41:25 AM skrev Johannes Ring <[email protected]>:

> On Tue, Jan 13, 2015 at 11:25 AM, Jan Blechta
> <[email protected]> wrote:
> > On Tue, 13 Jan 2015 11:18:52 +0100
> > Johannes Ring <[email protected]> wrote:
> >
> >> On Tue, Jan 13, 2015 at 11:12 AM, Jan Blechta
> >> <[email protected]> wrote:
> >> > On Mon, 12 Jan 2015 21:50:16 +0100
> >> > Johannes Ring <[email protected]> wrote:
> >> >
> >> >> 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?
> >> >
> >> > What about
> >> >
> >> > git checkout next
> >> > git reset --hard master
> >> > git push -f origin next
> >>
> >> Thanks, I will try that.
> >
> > Then it is usual to announce that next has been rewound on mailing-list
> > as it ruins others' fast-forwards. Everybody then should do
> >
> > git fetch origin
> > git checkout next
> > git reset --hard origin/next
> > git checkout master
> >
> > I believe - please test it.
>
> Thanks again. I have reset the branches and will announce it on the list.
>
> Johannes
> _______________________________________________
> fenics mailing list
> [email protected]
> http://fenicsproject.org/mailman/listinfo/fenics
>
_______________________________________________
fenics mailing list
[email protected]
http://fenicsproject.org/mailman/listinfo/fenics

Reply via email to