[Pharo-project] 3.9.1, version numbers and fixes
I'm a little bit confused. I started to have a look at the squeak fixes of 3dot10 we like to integrate. Looking at the version number I marked all version number up to 7075 as being duplicate (in the issue trackr) as we started from 3.9.1 which is 7075. But now I think I misunderstand something. I tried to merge squeak version 7076 into pharo. I did some stuff manually to be able to merge the monticello packages of that release. But the changes are massive. It's collections, collectionstests and kernel. There are even changes for widestring which I don't found in previous updates. Can somebody explain where we started off and what needs to be included. Pharo seems to be completely out of sync with 3.10. Norbert
On Jul 2, 2008, at 17:59 , Norbert Hartl wrote:
I'm a little bit confused. I started to have a look at the squeak fixes of 3dot10 we like to integrate. Looking at the version number I marked all version number up to 7075 as being duplicate (in the issue trackr) as we started from 3.9.1 which is 7075. But now I think I misunderstand something.
the numbers nnnn do not seem to be unique among 3.9 and 3.10. The reason likely is because 3.9.1 was done after 3.10 started, it continued numbering from 3.9 creating duplicates. You can see this in the update stream: http://ftp.squeak.org/updates/updates.list Therefore, the number alone does not uniquely identify the change.
I tried to merge squeak version 7076 into pharo. I did some stuff manually to be able to merge the monticello packages of that release. But the changes are massive. It's collections, collectionstests and kernel. There are even changes for widestring which I don't found in previous updates.
I think its easiest to load the changesets from Mantis into Pharo and then save a slice with the modified packages to the inbox. This will take quite some work, especially because we also need to check whether the fix makes sense and which changeset is the correct one if there are multiple ones etc. Can other people help with this? I suggest to change the status to "Started" when you start working on an issue to avoid conflicts. Adrian
On Jul 2, 2008, at 7:50 PM, Adrian Lienhard wrote:
On Jul 2, 2008, at 17:59 , Norbert Hartl wrote:
I'm a little bit confused. I started to have a look at the squeak fixes of 3dot10 we like to integrate. Looking at the version number I marked all version number up to 7075 as being duplicate (in the issue trackr) as we started from 3.9.1 which is 7075. But now I think I misunderstand something.
the numbers nnnn do not seem to be unique among 3.9 and 3.10. The reason likely is because 3.9.1 was done after 3.10 started, it continued numbering from 3.9 creating duplicates. You can see this in the update stream: http://ftp.squeak.org/updates/updates.list Therefore, the number alone does not uniquely identify the change.
Yes they did not let enough number for maintenance of 3.9 :(
I tried to merge squeak version 7076 into pharo. I did some stuff manually to be able to merge the monticello packages of that release. But the changes are massive. It's collections, collectionstests and kernel. There are even changes for widestring which I don't found in previous updates.
I think its easiest to load the changesets from Mantis into Pharo and then save a slice with the modified packages to the inbox. This will take quite some work, especially because we also need to check whether the fix makes sense and which changeset is the correct one if there are multiple ones etc.
Can other people help with this? I suggest to change the status to "Started" when you start working on an issue to avoid conflicts.
Adrian
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
participants (3)
-
Adrian Lienhard -
Norbert Hartl -
Stéphane Ducasse