dolfin team mailing list archive

[Anders Logg <logg@xxxxxxxxx>]

Good points all of them.

I think the main problem is that we have a general unreported bug
named something like "doesn't work as good in parallel as we could
hope", and fixing that bug requires quite a bit of coding. But I think
we need to postpone fixing that bug to after the release of 1.0.

--
Anders


On Wed, Oct 05, 2011 at 01:48:35PM +0200, Martin Sandve Alnæs wrote:
> Here's a mix of somewhat overlapping facts and my opinions, opinions
> may differ on which is which ;)
>
> - It is more imporant that FEniCS 1.0 corresponds with the book
> release than any single new feature. This has been promised publicly
> many times.
>
> - It is more important to have a stable bugfree 1.0 release than any
> single new feature. This requires a period of bugfixes only.
>
> - FEniCS won't stop developing after 1.0. Your favourite feature can wait.
>
> - Each new feature adds more test work. The beta so far have been more
> like an alpha, with several fairly big additions.
>
> - Many of my reported bugs the last couple of months have
> been related to feature changes from after mid June.
>
> - All new features can wait until post 1.0.
>
> - Release beta2 asap, do only bug fixes for a couple of weeks, release
> beta3, more bugfixes, release rc, hopefully no bugs to fix, release
> 1.0 final.
>
> - Bugfixes that requires redesign of any significant size should be
> postphoned, worked around, or otherwise managed in a way that doesn't
> incur major changes.
>
> If you want 1.0 released in a version that matches the book, you need
> to make releasing 1.0 the highest priority, above any new features. If
> 1.0 should be usable, it needs a testing period with only bugfixes.
>
> If some people need to continue working on features on the side,
> either do that in a side branch, or make a branch for 1.0-beta2.
> Bugfixes should then be done in the beta2 branch and merged into
> trunk.
>
> Martin
>
>
> On 5 October 2011 12:42, Anders Logg <logg@xxxxxxxxx> wrote:
> > What's everyone's thoughts on the pending release of 1.0 and addition
> > of new features?
> >
> > If we don't set a deadline or otherwise agree to get 1.0 out of the
> > door in the very near future, there's a chance that the list of bugs
> > and blueprints will continue to grow at a faster pace than we can fix
> > them.
> >
> > For example, I've started sketching out a new class UnassembledMatrix
> > which might help to improve the speed of assembly and possibly be used
> > for a redesign of SystemAssembler. I feel very tempted by it but at
> > the same time realize it should probably wait until 1.1.
> >
> > My suggestion is as follows:
> >
> > 1. Everyone take a look at blueprints/bugs targeted for 1.0-beta2:
> >
> >  https://launchpad.net/dolfin/+milestone/1.0-beta2
> >
> > Think about whether you can fix things today/tomorrow so we can make a
> > release of 1.0-beta2 this week. If not, move the items to 1.0-rc1.
> >
> > 2. Everyone take a look at blueprints/bugs targeted for 1.0-rc1:
> >
> >  https://launchpad.net/dolfin/+milestone/1.0-rc1
> >
> > Think about whether you can fix things within 2-3 weeks so we can make
> > a release of 1.0-rc1 by the end of the month. If not, discuss the
> > items in question on the mailing list and move to 1.1.
> >
> > ?
> >
> >
> > _______________________________________________
> > Mailing list: https://launchpad.net/~dolfin
> > Post to     : dolfin@xxxxxxxxxxxxxxxxxxx
> > Unsubscribe : https://launchpad.net/~dolfin
> > More help   : https://help.launchpad.net/ListHelp
> >