Hi everybody,
on SVN, I have created branches/4.0 to freeze version 4.0.0 Most changes necessary to release version 4.0.0 have been done. There are a few keywords/options that need to be added to the preprocessor and more tests need to be done. Please keep adding new features to the trunk (don't change anything to your SVN setup). If you want to test version 4.0.0, please check out branches/4.0 in a separate working directory, then commit only bug corrections from this working directory.
Best,
Michel
-------- Original Message -------- Subject: Re: SVN Date: Tue, 08 Jul 2008 17:40:56 +0200 From: Sébastien Villemot sebastien.villemot@ens.fr To: stephane.adjemian@ens.fr CC: Michel Juillard michel.juillard@ens.fr, George Perendia artilogica@btconnect.com References: 487370EC.4010500@ens.fr 200807081638.05166.stephane.adjemian@ens.fr 20080708165802.17365ydzqi1sg8sg@www.zelya.net 200807081712.03561.stephane.adjemian@ens.fr
Here is the timeline: * we finish Dynare 4.0.0 in the trunk (dynare_v4/) * when we're done, we copy dynare_v4/ to branches/4.0 and tags/4.0.0 * we fix bugs in branches/4.0, creating new releases when we feel the need (creating a release involves copying branches/4.0 to tags/4.0.x where x is the minor release number) * meanwhile, we add new features or restructure the code in the trunk (dynare_v4/). Also note that many bug fixes done on the 4.0 branch will also apply to the trunk * when we think we can make a new major release (for example when we've completed September 30 goals), we release 4.1.0 by copying dynare_v4/ to branches/4.1 and tags/4.1.0 * we continue the parallel development of the trunk, the 4.1 branch, and maybe the 4.0 branch (or we can decide to drop the 4.0 branch at that point)
Sébastien
"Stéphane Adjemian" stephane.adjemian@ens.fr a écrit :
So we use branches/4.0 to fix the bugs and use dynare_v4 to develop dynare. Am I right ? But what is the purpose of branches/4.1 (before the release of dynare 4.1.0) ?
Stéphane.
Le Tuesday 08 July 2008 16:58:02, vous avez écrit :
Under our current tree layout:
- dynare_v4/ is the trunk
- branches/ is for branches (for example branches/4.0/ or branches/4.1/)
- tags/ is for releases (tags/4.0.0, tags/4.0.1, ...)
Sébastien
"Stéphane Adjemian" stephane.adjemian@ens.fr a écrit :
I also agree with Sébastien suggestion (if the trunk is the current dynare_v4 directory under svn).
Stéphane.
Le Tuesday 08 July 2008 16:29:36 G. Perendia, vous avez écrit :
I support Sebastian's suggestion which, as he pointed out, is in line with the SW industry standard practices. We may also have the "traditional" "alpha" and "beta" releases (but that is just a matter of naming the X.0.0 and X.0.1 releases respectively).
Best regards
George Mob. +44(0)7951415480 artilogica@btconnect.com
----- Original Message ----- From: "Sébastien Villemot" sebastien.villemot@ens.fr To: "Michel Juillard" michel.juillard@ens.fr Cc: "George Perendia" artilogica@btconnect.com; "StéphaneAdjemian" stephane.adjemian@gmail.com Sent: Tuesday, July 08, 2008 3:12 PM Subject: Re: SVN
Concerning Dynare release schedule, one option would be the following:
- finish Dynare 4.0, and release version 4.0.0
- create a 4.0 branch in the SVN, used only for bugfixes; in other
words, versions 4.0.1, 4.0.2... would only incoporate bug fixes since 4.0.0, but no new feature nor code restructuring
- add new features or code restructurings in the trunk; the trunk will
later become the 4.1 branch (maybe for the September 30 deadline)
- and so on at each major release/deadline...
This model of development is used in many softwares. Its main interest is that it produces very stable software at the end of a development branch, since no new feature can destabilize the code along a branch. On the other hand, it involves some overhead related to the simultaneous management of a branch and a trunk (a bugfix needs often to be applied to both).
Do you think it is a sensible development model for Dynare?
Best
Sébastien
"Michel Juillard" michel.juillard@ens.fr a écrit :
I have added 'george' as username authorized to commit on the SVN archive. The password is as mentioned at the Summer School. George will also get the email messages after each commit.
Stephane, I checked that these messages go for you at stephane.adjemian@ens.fr. Is it what you want?
best
Michel