fenics team mailing list archive
-
fenics team
-
Mailing list archive
-
Message #01870
FEniCS releases and appointing a release manager
-
To:
fenics@xxxxxxxxxxxxxxxxxxx
-
From:
"Marie E. Rognes" <meg@xxxxxxxxx>
-
Date:
Wed, 20 Feb 2013 15:18:52 +0100
-
User-agent:
Mozilla/5.0 (X11; Linux x86_64; rv:16.0) Gecko/20121028 Thunderbird/16.0.2
Hi,
I would like to follow-up on previous discussions in other fora
regarding FEniCS releases: we would like to make releases more often,
how do we ensure that that actually happens?
In order to make it happen, I suggest we appoint a permanent[1]
release manager who is responsible for initiating releases at a
suitable, pre-defined frequency, and for driving the release process
in accordance with the development model[2]. A frequency of
approximately once every three months has been mentioned before, but
this can of course be discussed further.
Moreover, I've talked to Johannes about this -- and he is willing to
and interested in doing this job :-) Frequent releases would ensure
that the release scripts are up to date and Johannes (and others) have
indicated that most of the button-clicking on Launchpad indeed can be
scripted via the Launchpad API.
Sidenote: I think that this is a good way to go regardless of whether
the FEniCS components are kept as is or if we decide to go for a more
unified approach (UFR).
Comments/Objections/All in favor?
Thanks,
Marie
[1] Meaning: until further notice
[2] in particular, steps 3.-7. listed here
http://fenicsproject.org/contributing/development_model.html)
Follow ups