New Jul2017 stable branch created
I have created a new stable branch for the next feature release. This branch was created in order to stabilize the code before the feature release. From now on *only* bug fixes may go to this new stable branch. I reserve the right to undo any changes that do not comply with this rule. I also reserve the right to admit changes that are not strictly bug fixes. The name for the branch is Jul2017. So in each of your stable checkout directories you can do hg pull hg update -rJul2017 to update to this new branch. -- Sjoerd Mullender
I've noticed the GDKLIBRARY version has been bumped twice since the last feature release: Once in changest f054b7310be7, during a merge with the default branch, to fix a string duplication bug; but also once before, in changeset 0c475cc54c60; the log suggests that bump was also related to the same duplicate-empty-string issue. So, * Which of these changes involved a change to the actual format on disk, as opposed to a change to the MonetDB code reading it? * How possible is it for there to be another BBP format change before the next feature release? Eyal On 04/24/2017 02:28 PM, Sjoerd Mullender wrote:
I have created a new stable branch for the next feature release. This branch was created in order to stabilize the code before the feature release.
From now on *only* bug fixes may go to this new stable branch. I reserve the right to undo any changes that do not comply with this rule. I also reserve the right to admit changes that are not strictly bug fixes.
The name for the branch is Jul2017. So in each of your stable checkout directories you can do hg pull hg update -rJul2017 to update to this new branch.
_______________________________________________ developers-list mailing list developers-list@monetdb.org https://www.monetdb.org/mailman/listinfo/developers-list
Those two changesets are sort-of the same. 0c475cc54c60 was done on the Dec2016 branch and involved a fix to the string heaps that needed to be done. There is no change in the format of the BBP.dir file. f054b7310be7 is the merge of this change into the default branch. Earlier on the default branch I had made a change that did change the format of the BBP.dir file (changeset 1b509f7422bb). The merge in f054b7310be7 changed the GDK version number for this change creating a discontinuity in the versioning. There is no upgrade path from a database created (or updated to) a changeset between 1b509f7422bb and f054b7310be7 on the default branch and a version after the latter changeset on the default (or now Jul2017) branch. I cannot predict the future, so I don't know whether there will be another format change to the BBP.dir file before the actual Jul2017 release. On 24/04/17 14:48, Eyal Rozenberg wrote:
I've noticed the GDKLIBRARY version has been bumped twice since the last feature release: Once in changest f054b7310be7, during a merge with the default branch, to fix a string duplication bug; but also once before, in changeset 0c475cc54c60; the log suggests that bump was also related to the same duplicate-empty-string issue. So,
* Which of these changes involved a change to the actual format on disk, as opposed to a change to the MonetDB code reading it? * How possible is it for there to be another BBP format change before the next feature release?
Eyal
On 04/24/2017 02:28 PM, Sjoerd Mullender wrote:
I have created a new stable branch for the next feature release. This branch was created in order to stabilize the code before the feature release.
From now on *only* bug fixes may go to this new stable branch. I reserve the right to undo any changes that do not comply with this rule. I also reserve the right to admit changes that are not strictly bug fixes.
The name for the branch is Jul2017. So in each of your stable checkout directories you can do hg pull hg update -rJul2017 to update to this new branch.
_______________________________________________ developers-list mailing list developers-list@monetdb.org https://www.monetdb.org/mailman/listinfo/developers-list
_______________________________________________ developers-list mailing list developers-list@monetdb.org https://www.monetdb.org/mailman/listinfo/developers-list
-- Sjoerd Mullender
participants (3)
-
Eyal Rozenberg -
Sjoerd Mullender -
Sjoerd Mullender