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
<[EMAIL PROTECTED]> 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
[email protected]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________
Pharo-project mailing list
[email protected]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________
Pharo-project mailing list
[email protected]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
