[Monetdb-developers] Release schedule
Today we decided that we want to try to do releases more often and more regularly. I have been appointed release manager for all upcoming releases.
I propose that we keep to the following schedule:
- Do a major (feature) release once every 4 months. - Do a minor (bug fix) release once every month inbetween the major releases.
This should solve the problem that we get bug reports for problems in the release for bugs that were already fixed months ago but not yet released. In the worst case the submitter has to wait a month for the fix, but usually of course much less than that. It also solves the problem that developers always want to add just one more feature to the next release and thereby forcing the release to be postponed. If a feature doesn't make it in a release, it will be released in four months time. If users (and developers) had to wait years for this feature, they can wait a little longer.
I also propose to create a new stable branch right after releasing the last of the bug fix releases in a cycle. This gives us one month to stabilize and test a new release.
This plan is effective as of now.
On 2008-11-04 20:36, Stefan de Konink wrote:
Sjoerd Mullender wrote:
- Do a minor (bug fix) release once every month inbetween the major
releases.
Would it be possible to automatically rebuild the 'stable' release after a bug has been fixed? So some sort of 'on demand' releasing?
Stefan
No. But you can always try to get the nightly builds (if the build succeeded). You only need to wait to the next day.
Sjoerd Mullender wrote:
On 2008-11-04 20:36, Stefan de Konink wrote:
Sjoerd Mullender wrote:
- Do a minor (bug fix) release once every month inbetween the major
releases.
Would it be possible to automatically rebuild the 'stable' release after a bug has been fixed? So some sort of 'on demand' releasing?
Stefan
No. But you can always try to get the nightly builds (if the build succeeded). You only need to wait to the next day.
Ok; that basically does what I suggest. But the question is why build at night if there are no changes.
Stefan
On 04-11-2008 20:44:39 +0100, Stefan de Konink wrote:
Sjoerd Mullender wrote:
On 2008-11-04 20:36, Stefan de Konink wrote:
Sjoerd Mullender wrote:
- Do a minor (bug fix) release once every month inbetween the major
releases.
Would it be possible to automatically rebuild the 'stable' release after a bug has been fixed? So some sort of 'on demand' releasing?
Stefan
No. But you can always try to get the nightly builds (if the build succeeded). You only need to wait to the next day.
Ok; that basically does what I suggest. But the question is why build at night if there are no changes.
If there are no changes, we've been doing nothing. If we've been doing nothing, we've not been productive. If we've not been productive, we won't get world domination. If we won't get world domination, we get sad.
anyway...
Fabian Groffen wrote:
If there are no changes, we've been doing nothing.
You would have worked hard on the unstable branch >: )
If we've been doing nothing, we've not been productive.
Or working on the feature request tracker (hint).
If we've not been productive, we won't get world domination.
I would suggest another approach; but since you already operate a community website you must have access to that >: )
If we won't get world domination, we get sad.
True; I don't want that to happen. I will not swear with the O-word on this mailinglist!
Stefan
On Tue, Nov 04, 2008 at 08:44:39PM +0100, Stefan de Konink wrote:
Sjoerd Mullender wrote:
On 2008-11-04 20:36, Stefan de Konink wrote:
Sjoerd Mullender wrote:
- Do a minor (bug fix) release once every month inbetween the major
releases.
Would it be possible to automatically rebuild the 'stable' release after a bug has been fixed? So some sort of 'on demand' releasing?
Stefan
No. But you can always try to get the nightly builds (if the build succeeded). You only need to wait to the next day.
Ok; that basically does what I suggest. But the question is why build at night if there are no changes.
because we test every night, even if there happen to be no changes to the code just to make sure that we are not "surprised" by non-communicated changes to our testing systems ...
Stefan
Stefan
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Monetdb-developers mailing list Monetdb-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/monetdb-developers
On Tue, Nov 04, 2008 at 08:36:50PM +0100, Stefan de Konink wrote:
Sjoerd Mullender wrote:
- Do a minor (bug fix) release once every month inbetween the major
releases.
Would it be possible to automatically rebuild the 'stable' release after a bug has been fixed? So some sort of 'on demand' releasing?
Source tarballs are available as nightly builds from
http://monetdb.cwi.nl/projects/monetdb/Download/Builds/index.html http://monetdb.cwi.nl/testing/projects/monetdb/Stable/.DailyBuilds./ http://monetdb.cwi.nl/testing/projects/monetdb/Stable/.DailyBuilds./0_latest... http://monetdb.cwi.nl/testing/projects/monetdb/Stable/.DailyBuilds./0_latest... http://monetdb.cwi.nl/testing/projects/monetdb/Stable/.DailyBuilds./0_latest...
(The RPMs that you might find there are not workig properly.)
(Working) binary releases (Windows installers, Fedora RPMs, Ubuntu/Debian PKGs) are not yet build during nightly testing --- adding such feature is on our agenda, but might take some time given time, manpower and resource limitations ...
Stefan
Stefan
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Monetdb-developers mailing list Monetdb-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/monetdb-developers
participants (4)
-
Fabian Groffen -
Sjoerd Mullender -
Stefan de Konink -
Stefan Manegold