dolfin team mailing list archive

[Andre Massing <massing@xxxxxxxxx>]

Andre Massing wrote:
> Anders Logg wrote:
> > On Sat, Nov 28, 2009 at 10:21:18PM +0000, Garth N. Wells wrote:
> > > Anders Logg wrote:
> > > > On Sat, Nov 28, 2009 at 09:32:03PM +0000, Garth N. Wells wrote:
> > > > > It would be good to make a release of DOLFIN/FFL/UFL next week with 
> > > > > the
> > > > > new syntax for Constants and Expressions. Are there any pressing 
> > > > > issues
> > > > > which need to be addressed before making a new release?
> > > > >
> > > > > Garth
> > > > I agree. Let's make a release as soon as possible.
> > > >
> > > > The only things I see missing are
> > > >
> > > > 1. std::vector argument in eval. I see you've started on this.
> > > >
> > > > 2. Getting the buildbot running in on form or another.
> > > If we don't get this running in time, I'm happy if we run the tests by
> > > hand on a few OSes.
> >
> > Me too.
> >
> > > > Andre Massing has prepared a major bundle on the CGAL stuff but that
> > > > can wait until after 0.9.5, but it would be good to do it immediately
> > > > after so we get that done.
> > > Perhaps he could publish it first as a personal branch on Launchpad?
> >
> > Yes, it would be a good opportunity to test that feature.
> >
> > What do you think Andre? Could you give it a try?
>
> Yes, sounds like a good idea to me. So far almost everything should be 
> in place, although I still have some ideas in mind I would like to 
> implement :) But I would like to get the CGAL stuff merged ASAP, merging 
> everything via diff/patch by into the new bzr branch locally on my disk 
> and not getting the my converted branch into trunk was a kind of a 
> painful experience :(
>
> And using the launchpad branch feature is a good way to get the code 
> reviewed by the dolfin developers :)
> I will install a branch tomorrow/today...

So, I published a branch, accessible via
bzr branch lp:~massing/dolfin/cgal_branch

I came across with a few lp related questions:

1. I had a bug, introduce by some template clean-ups which is now fixed.
Therefore I wanted to report a bug with respect to a certain branch. The 
only possibility I found so far, was to report a general dolfin related 
bug and afterwards to link it the branch. But is not obvious, that 
affects only that brunch.
http://doc.bazaar-vcs.org/bzr.2.0/en/tutorials/using_bazaar_with_launchpad.html#associating-a-branch-with-a-bug
said something about this, but I only found a "Link a related branch" 
button with no options to set the relationship.

2. I am wondering whether the dolfin ml list automatically obtains 
notification about events concerning this branch? (At least ml is noted 
as "Notified", but not as subscribers.

3. I could assign the bug to me and set it fix committed. But it does 
not seem to work automatically with the combination "bzr commit --fixes 
lp:<bugnummer>" + bzr push ... Hmm or this the latency of lp rather high?

4. Does anybody use the bzr-search plugin? Unfortunately the bzr index 
command segfaults on my machine, so I am missing advanced search 
features, e.g looking for commits from certain persons etc.
(Hmm, already missing quite a few very neat hg tools ;))


Greetings,
Andre




> > --
> > Anders
>
> _______________________________________________
> Mailing list: https://launchpad.net/~dolfin
> Post to     : dolfin@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~dolfin
> More help   : https://help.launchpad.net/ListHelp