[Pharo-project] How to follow which packages have been integrated ,
I still have some difficulties to know exactly what have been integrated in Pharo after putting some .mcz in the PharoInbox. I have to check manually if packages have been integrated or just put in PharoTreated (and i to repropose another version of the fix to the PharoInbox repository). It's even more difficult when the name packages have been renamed and/or the comments modified. What the others are doing ? Thank you for your attention. -- Serge Stinckwich Smalltalkers do: [:it | All with: Class, (And love: it)] http://blog.doesnotunderstand.org/
On Sat, 2008-07-05 at 00:16 +0200, Serge Stinckwich wrote:
I still have some difficulties to know exactly what have been integrated in Pharo after putting some .mcz in the PharoInbox. I have to check manually if packages have been integrated or just put in PharoTreated (and i to repropose another version of the fix to the PharoInbox repository).
That is one of the reasons why I find it important to open issues on all fixes. When the package is harvested there should be a comment at the end of this issue which version includes your changes.
It's even more difficult when the name packages have been renamed and/or the comments modified. What the others are doing ? Thank you for your attention.
I don't understand what you mean. Can you elaborate? Norbert
On Sat, Jul 5, 2008 at 12:16 AM, Serge Stinckwich <serge.stinckwich@doesnotunderstand.org> wrote:
I still have some difficulties to know exactly what have been integrated in Pharo after putting some .mcz in the PharoInbox. I have to check manually if packages have been integrated or just put in PharoTreated (and i to repropose another version of the fix to the PharoInbox repository).
What about a PharoRejected box? -- Damien Cassou Peter von der Ahé: «I'm beginning to see why Gilad wished us good luck». (http://blogs.sun.com/ahe/entry/override_snafu)
2008/7/5 Norbert Hartl <norbert@hartl.name>:
On Sat, 2008-07-05 at 00:16 +0200, Serge Stinckwich wrote:
I still have some difficulties to know exactly what have been integrated in Pharo after putting some .mcz in the PharoInbox. I have to check manually if packages have been integrated or just put in PharoTreated (and i to repropose another version of the fix to the PharoInbox repository).
That is one of the reasons why I find it important to open issues on all fixes. When the package is harvested there should be a comment at the end of this issue which version includes your changes.
It's even more difficult when the name packages have been renamed and/or the comments modified. What the others are doing ? Thank you for your attention.
I don't understand what you mean. Can you elaborate?
For example, Stéphane renamed my package deposed in PharoInbox (and now in PharoTreated) : Collections-zz.85.mcz into Collections-stephaneducasse.86.mcz (in Pharo) ... It's almost impossible to follow what packages have been integrated or not. It's not a negative remark from me, i just observe that it doesn't scale well ... -- Serge Stinckwich Smalltalkers do: [:it | All with: Class, (And love: it)] http://blog.doesnotunderstand.org/
2008/7/6 Damien Cassou <damien.cassou@gmail.com>:
On Sat, Jul 5, 2008 at 12:16 AM, Serge Stinckwich <serge.stinckwich@doesnotunderstand.org> wrote:
I still have some difficulties to know exactly what have been integrated in Pharo after putting some .mcz in the PharoInbox. I have to check manually if packages have been integrated or just put in PharoTreated (and i to repropose another version of the fix to the PharoInbox repository).
What about a PharoRejected box?
Hum even more difficult i guess (because you have to watch 4 separate repositories) and we have no explanations why a package is in PharoTreated or PharoRejected box ... -- Serge Stinckwich Smalltalkers do: [:it | All with: Class, (And love: it)] http://blog.doesnotunderstand.org/
I don't understand what you mean. Can you elaborate?
For example, Stéphane renamed my package deposed in PharoInbox (and now in PharoTreated) : Collections-zz.85.mcz into Collections-stephaneducasse.86.mcz (in Pharo) ... It's almost impossible to follow what packages have been integrated or not. It's not a negative remark from me, i just observe that it doesn't scale well ...
Yes I know. The problem is that the harvesters have to merge your changes. Else we could rollback other fixes. And when we merge we get newer versions. Tell me how we can improve that. Stef
why not. I think that this may improve communication. the harvested will have to be more cautious but this is ok for me.
<serge.stinckwich@doesnotunderstand.org> wrote:
I still have some difficulties to know exactly what have been integrated in Pharo after putting some .mcz in the PharoInbox. I have to check manually if packages have been integrated or just put in PharoTreated (and i to repropose another version of the fix to the PharoInbox repository).
What about a PharoRejected box?
-- Damien Cassou Peter von der Ahé: «I'm beginning to see why Gilad wished us good luck». (http://blogs.sun.com/ahe/entry/override_snafu)
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
I think the issue tracker should reflect all changes. Like this, to see whether something is harvested you look there instead of the SqueakSource repository. I think Stef always updates the status of the issues when pushing them into the update stream. When they are rejected there exists also a special state for this situation. So maybe PharoRejected is not needed, not sure. Adrian On Jul 8, 2008, at 10:21 , Stéphane Ducasse wrote:
why not. I think that this may improve communication. the harvested will have to be more cautious but this is ok for me.
<serge.stinckwich@doesnotunderstand.org> wrote:
I still have some difficulties to know exactly what have been integrated in Pharo after putting some .mcz in the PharoInbox. I have to check manually if packages have been integrated or just put in PharoTreated (and i to repropose another version of the fix to the PharoInbox repository).
What about a PharoRejected box?
-- Damien Cassou Peter von der Ahé: «I'm beginning to see why Gilad wished us good luck». (http://blogs.sun.com/ahe/entry/override_snafu)
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
On Tue, 2008-07-08 at 15:16 +0300, Adrian Lienhard wrote:
I think the issue tracker should reflect all changes. Like this, to see whether something is harvested you look there instead of the SqueakSource repository. I think Stef always updates the status of the issues when pushing them into the update stream. When they are rejected there exists also a special state for this situation.
So maybe PharoRejected is not needed, not sure.
+1 We should use the tool as far as we can. Stef does indeed add a comment to the ticket if he harvests it. We did even add a note to mantis on bugs.squeak.org if the bug is harvested in pharo. Norbert
Adrian
On Jul 8, 2008, at 10:21 , Stéphane Ducasse wrote:
why not. I think that this may improve communication. the harvested will have to be more cautious but this is ok for me.
<serge.stinckwich@doesnotunderstand.org> wrote:
I still have some difficulties to know exactly what have been integrated in Pharo after putting some .mcz in the PharoInbox. I have to check manually if packages have been integrated or just put in PharoTreated (and i to repropose another version of the fix to the PharoInbox repository).
What about a PharoRejected box?
-- Damien Cassou Peter von der Ahé: «I'm beginning to see why Gilad wished us good luck». (http://blogs.sun.com/ahe/entry/override_snafu)
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Yes we did that like that in mantis for 3.9 And this is the minimum we should do. stef On Jul 8, 2008, at 2:34 PM, Norbert Hartl wrote:
On Tue, 2008-07-08 at 15:16 +0300, Adrian Lienhard wrote:
I think the issue tracker should reflect all changes. Like this, to see whether something is harvested you look there instead of the SqueakSource repository. I think Stef always updates the status of the issues when pushing them into the update stream. When they are rejected there exists also a special state for this situation.
So maybe PharoRejected is not needed, not sure.
+1
We should use the tool as far as we can. Stef does indeed add a comment to the ticket if he harvests it. We did even add a note to mantis on bugs.squeak.org if the bug is harvested in pharo.
Norbert
Adrian
On Jul 8, 2008, at 10:21 , Stéphane Ducasse wrote:
why not. I think that this may improve communication. the harvested will have to be more cautious but this is ok for me.
<serge.stinckwich@doesnotunderstand.org> wrote:
I still have some difficulties to know exactly what have been integrated in Pharo after putting some .mcz in the PharoInbox. I have to check manually if packages have been integrated or just put in PharoTreated (and i to repropose another version of the fix to the PharoInbox repository).
What about a PharoRejected box?
-- Damien Cassou Peter von der Ahé: «I'm beginning to see why Gilad wished us good luck». (http://blogs.sun.com/ahe/entry/override_snafu)
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
On Mon, Jul 7, 2008 at 5:40 PM, Serge Stinckwich <serge.stinckwich@doesnotunderstand.org> wrote: [snip]
For example, Stéphane renamed my package deposed in PharoInbox (and now in PharoTreated) : Collections-zz.85.mcz into Collections-stephaneducasse.86.mcz (in Pharo) ... It's almost impossible to follow what packages have been integrated or not.
There is a very easy way to fix this: include the issue number in the package name. So how is this for a proposal: there should be an issue filed for everything that goes into the image, and every package that goes into the inbox should include in the name the issue number. Best Regards, Victor Fodirguez.
It's not a negative remark from me, i just observe that it doesn't scale well ... -- Serge Stinckwich Smalltalkers do: [:it | All with: Class, (And love: it)] http://blog.doesnotunderstand.org/
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Hi Victor Thanks for the suggestion. I would stick with using the issue tracker as the primary place to track changes. Else you end up having to update at look at multiple places. That said, I think it makes sense to just add the issue number in the comment of the package, but this should just serve as additional information. I would not put it into the file name. Especially because when doing an update we often have to merge packages and then this just becomes unusable. In summary, to see whether a package has been integrated, look at the issue you created. Cheers, Adrian On Jul 11, 2008, at 20:20 , Victor Rodriguez wrote:
On Mon, Jul 7, 2008 at 5:40 PM, Serge Stinckwich <serge.stinckwich@doesnotunderstand.org> wrote: [snip]
For example, Stéphane renamed my package deposed in PharoInbox (and now in PharoTreated) : Collections-zz.85.mcz into Collections-stephaneducasse.86.mcz (in Pharo) ... It's almost impossible to follow what packages have been integrated or not.
There is a very easy way to fix this: include the issue number in the package name.
So how is this for a proposal: there should be an issue filed for everything that goes into the image, and every package that goes into the inbox should include in the name the issue number.
Best Regards,
Victor Fodirguez.
It's not a negative remark from me, i just observe that it doesn't scale well ... -- Serge Stinckwich Smalltalkers do: [:it | All with: Class, (And love: it)] http://blog.doesnotunderstand.org/
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
participants (6)
-
Adrian Lienhard -
Damien Cassou -
Norbert Hartl -
Serge Stinckwich -
Stéphane Ducasse -
Victor Rodriguez