[Pharo-project] 3dot10 fixes
I had a look at the wiki page of 3dot10 fixes. The wiki page is good but I have the impression that putting all changes in the issue tracker could be worth it. I would create another type Type-squeak to track every update from squeak. I would prefer not to put the mantis issues into it but each squeak version. That would enable us to see if we are in sync with squeak. What do you think? I could do it in the next spare time. Norbert
On Jul 1, 2008, at 22:11 , Norbert Hartl wrote:
I had a look at the wiki page of 3dot10 fixes.
do you mean this page? http://code.google.com/p/pharo/wiki/ThreeDotTenFixes We need to check, I think it does not contain all changes because the final 3.10 image has version number 7159. (We should also not forget that there is a 3.10.1 and 3.10.2 with more changes.)
The wiki page is good but I have the impression that putting all changes in the issue tracker could be worth it.
If you think its not too much work, go for it.
I would create another type Type-squeak to track every update from squeak. I would prefer not to put the mantis issues into it but each squeak version. That would enable us to see if we are in sync with squeak.
But I would still point to the Mantis report since it contains important information.
What do you think? I could do it in the next spare time.
That would be great. I can have a second look after you are done. Adrian
Norbert
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Ticketing system are better so if you can do it. Please do it.
I had a look at the wiki page of 3dot10 fixes.
do you mean this page? http://code.google.com/p/pharo/wiki/ThreeDotTenFixes We need to check, I think it does not contain all changes because the final 3.10 image has version number 7159. (We should also not forget that there is a 3.10.1 and 3.10.2 with more changes.)
The wiki page is good but I have the impression that putting all changes in the issue tracker could be worth it.
If you think its not too much work, go for it.
I would create another type Type-squeak to track every update from squeak. I would prefer not to put the mantis issues into it but each squeak version. That would enable us to see if we are in sync with squeak.
But I would still point to the Mantis report since it contains important information.
Yes
What do you think? I could do it in the next spare time.
That would be great. I can have a second look after you are done.
Yes me too since I started to go over the list. Stef
Adrian
Norbert
_______________________________________________ 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-01 at 23:09 +0200, Adrian Lienhard wrote:
On Jul 1, 2008, at 22:11 , Norbert Hartl wrote:
I had a look at the wiki page of 3dot10 fixes.
do you mean this page? http://code.google.com/p/pharo/wiki/ThreeDotTenFixes We need to check, I think it does not contain all changes because the final 3.10 image has version number 7159. (We should also not forget that there is a 3.10.1 and 3.10.2 with more changes.)
The wiki page is good but I have the impression that putting all changes in the issue tracker could be worth it.
If you think its not too much work, go for it.
I would create another type Type-squeak to track every update from squeak. I would prefer not to put the mantis issues into it but each squeak version. That would enable us to see if we are in sync with squeak.
But I would still point to the Mantis report since it contains important information.
Yes, I just meant that the type of the issues won't be Type-Mantis. It would be Type-Squeak instead. I include the reference to mantis in the bug description. A minute ago I found that I can't create links in issues. That is annoying. I will include them as text by now. I'm starting to dislike google code. Norbert
What do you think? I could do it in the next spare time.
That would be great. I can have a second look after you are done.
Adrian
Norbert
_______________________________________________ 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 Wed, Jul 02, 2008 at 09:29:07AM +0200, Norbert Hartl wrote:
I'm starting to dislike google code.
on bugs.squeak.org, there is a project named Pharo. Stef is probably the administrator. I'm sure you know how to use mantis -- Matthew Fulmer -- http://mtfulmer.wordpress.com/
On Wed, 2008-07-02 at 00:39 -0700, Matthew Fulmer wrote:
On Wed, Jul 02, 2008 at 09:29:07AM +0200, Norbert Hartl wrote:
I'm starting to dislike google code.
on bugs.squeak.org, there is a project named Pharo. Stef is probably the administrator.
I'm sure you know how to use mantis
Yes I know. But we you are proposing this. We decided to use google code. What do you mean? Norbert
Matthew, we decided to use Google code instead of Mantis or another bug tracker. All systems have their pros and cons, but personally I like Google code, and that's what we are using now. The Pharo project on Mantis should be deleted. Adrian On Jul 2, 2008, at 09:39 , Matthew Fulmer wrote:
On Wed, Jul 02, 2008 at 09:29:07AM +0200, Norbert Hartl wrote:
I'm starting to dislike google code.
on bugs.squeak.org, there is a project named Pharo. Stef is probably the administrator.
I'm sure you know how to use mantis
-- Matthew Fulmer -- http://mtfulmer.wordpress.com/
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Adrian Lienhard wrote:
Matthew, we decided to use Google code instead of Mantis or another bug tracker. All systems have their pros and cons, but personally I like Google code, and that's what we are using now.
What about pure Smalltalk SPM (Squeak Project Manager) by Nicolas Petton? See for example SPM for Scribo project: http://scribo.bioskop.fr. Besides issue tracker there is also a Wiki and repository browser. SPM is still in development but with more usage I'm sure Nicolas will speed up work. But comparing with Google Code, we are near already, IMHO. What do you think? Janko
On Jul 2, 2008, at 09:39 , Matthew Fulmer wrote:
On Wed, Jul 02, 2008 at 09:29:07AM +0200, Norbert Hartl wrote:
I'm starting to dislike google code.
on bugs.squeak.org, there is a project named Pharo. Stef is probably the administrator.
I'm sure you know how to use mantis
--Matthew Fulmer -- http://mtfulmer.wordpress.com/
-- Janko Mivšek Svetovalec za informatiko Eranova d.o.o. Ljubljana, Slovenija www.eranova.si tel: 01 514 22 55 faks: 01 514 22 56 gsm: 031 674 565
Hi Janko, On Jul 2, 2008, at 10:27 , Janko Mivšek wrote:
Adrian Lienhard wrote:
Matthew, we decided to use Google code instead of Mantis or another bug tracker. All systems have their pros and cons, but personally I like Google code, and that's what we are using now.
What about pure Smalltalk SPM (Squeak Project Manager) by Nicolas Petton? See for example SPM for Scribo project: http://scribo.bioskop.fr . Besides issue tracker there is also a Wiki and repository browser.
I do not find an issue tracker on http://scribo.bioskop.fr. Have I missed something?
SPM is still in development but with more usage I'm sure Nicolas will speed up work. But comparing with Google Code, we are near already, IMHO. What do you think?
I think we should not change again now. We already migrated from http://pharo.gforge.inria.fr/ to Google code and it works fairly well. I think we should reconsider this decision at a later point. Adrian
Janko
On Jul 2, 2008, at 09:39 , Matthew Fulmer wrote:
On Wed, Jul 02, 2008 at 09:29:07AM +0200, Norbert Hartl wrote:
I'm starting to dislike google code.
on bugs.squeak.org, there is a project named Pharo. Stef is probably the administrator.
I'm sure you know how to use mantis
--Matthew Fulmer -- http://mtfulmer.wordpress.com/
-- Janko Mivšek Svetovalec za informatiko Eranova d.o.o. Ljubljana, Slovenija www.eranova.si tel: 01 514 22 55 faks: 01 514 22 56 gsm: 031 674 565
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
On Wed, 2008-07-02 at 10:48 +0200, Adrian Lienhard wrote:
Hi Janko,
On Jul 2, 2008, at 10:27 , Janko Mivšek wrote:
Adrian Lienhard wrote:
Matthew, we decided to use Google code instead of Mantis or another bug tracker. All systems have their pros and cons, but personally I like Google code, and that's what we are using now.
What about pure Smalltalk SPM (Squeak Project Manager) by Nicolas Petton? See for example SPM for Scribo project: http://scribo.bioskop.fr . Besides issue tracker there is also a Wiki and repository browser.
I do not find an issue tracker on http://scribo.bioskop.fr. Have I missed something?
SPM is still in development but with more usage I'm sure Nicolas will speed up work. But comparing with Google Code, we are near already, IMHO. What do you think?
I think we should not change again now. We already migrated from http://pharo.gforge.inria.fr/ to Google code and it works fairly well. I think we should reconsider this decision at a later point.
+1 Changing again would be pure pain :) And the tool doesn't really matter if you get it done. It's the people using it. Norbert
Adrian
Janko
On Jul 2, 2008, at 09:39 , Matthew Fulmer wrote:
On Wed, Jul 02, 2008 at 09:29:07AM +0200, Norbert Hartl wrote:
I'm starting to dislike google code.
on bugs.squeak.org, there is a project named Pharo. Stef is probably the administrator.
I'm sure you know how to use mantis
--Matthew Fulmer -- http://mtfulmer.wordpress.com/
-- Janko Mivšek Svetovalec za informatiko Eranova d.o.o. Ljubljana, Slovenija www.eranova.si tel: 01 514 22 55 faks: 01 514 22 56 gsm: 031 674 565
_______________________________________________ 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
We just change the issue tool, so we don't want to change again right now. I think we could change in the future, when we want a complete self-hosting issue tracker. 2008/7/2 Norbert Hartl <norbert@hartl.name>:
On Wed, 2008-07-02 at 10:48 +0200, Adrian Lienhard wrote:
Hi Janko,
On Jul 2, 2008, at 10:27 , Janko Mivšek wrote:
Adrian Lienhard wrote:
Matthew, we decided to use Google code instead of Mantis or another bug tracker. All systems have their pros and cons, but personally I like Google code, and that's what we are using now.
What about pure Smalltalk SPM (Squeak Project Manager) by Nicolas Petton? See for example SPM for Scribo project: http://scribo.bioskop.fr . Besides issue tracker there is also a Wiki and repository browser.
I do not find an issue tracker on http://scribo.bioskop.fr. Have I missed something?
SPM is still in development but with more usage I'm sure Nicolas will speed up work. But comparing with Google Code, we are near already, IMHO. What do you think?
I think we should not change again now. We already migrated from http://pharo.gforge.inria.fr/ to Google code and it works fairly well. I think we should reconsider this decision at a later point.
+1
Changing again would be pure pain :) And the tool doesn't really matter if you get it done. It's the people using it.
Norbert
Adrian
Janko
On Jul 2, 2008, at 09:39 , Matthew Fulmer wrote:
On Wed, Jul 02, 2008 at 09:29:07AM +0200, Norbert Hartl wrote:
I'm starting to dislike google code.
on bugs.squeak.org, there is a project named Pharo. Stef is probably the administrator.
I'm sure you know how to use mantis
--Matthew Fulmer -- http://mtfulmer.wordpress.com/
-- Janko Mivšek Svetovalec za informatiko Eranova d.o.o. Ljubljana, Slovenija www.eranova.si tel: 01 514 22 55 faks: 01 514 22 56 gsm: 031 674 565
_______________________________________________ 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
-- Serge Stinckwich Smalltalkers do: [:it | All with: Class, (And love: it)] http://blog.doesnotunderstand.org/
+ 1
SPM is still in development but with more usage I'm sure Nicolas will speed up work. But comparing with Google Code, we are near already, IMHO. What do you think?
I think we should not change again now. We already migrated from http://pharo.gforge.inria.fr/ to Google code and it works fairly well. I think we should reconsider this decision at a later point.
+1
Changing again would be pure pain :) And the tool doesn't really matter if you get it done. It's the people using it.
Ok guys, understandable. Also let the SPM evolve a bit more to the point that you won't hesitate a minute to switch to it :) Janko Stéphane Ducasse wrote:
+ 1
SPM is still in development but with more usage I'm sure Nicolas will speed up work. But comparing with Google Code, we are near already, IMHO. What do you think?
I think we should not change again now. We already migrated from http://pharo.gforge.inria.fr/ to Google code and it works fairly well. I think we should reconsider this decision at a later point.
+1
Changing again would be pure pain :) And the tool doesn't really matter if you get it done. It's the people using it.
-- Janko Mivšek AIDA/Web Smalltalk Web Application Server http://www.aidaweb.si
exactly. I think that you can learn from code google and having a good tracker may be using magritte would be good. Stef On Jul 2, 2008, at 12:30 PM, Janko Mivšek wrote:
Ok guys, understandable. Also let the SPM evolve a bit more to the point that you won't hesitate a minute to switch to it :)
Janko
Stéphane Ducasse wrote:
+ 1
SPM is still in development but with more usage I'm sure Nicolas will speed up work. But comparing with Google Code, we are near already, IMHO. What do you think?
I think we should not change again now. We already migrated from http://pharo.gforge.inria.fr/ to Google code and it works fairly well. I think we should reconsider this decision at a later point.
+1
Changing again would be pure pain :) And the tool doesn't really matter if you get it done. It's the people using it.
-- Janko Mivšek AIDA/Web Smalltalk Web Application Server http://www.aidaweb.si
_______________________________________________ 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 -
Janko Mivšek -
Matthew Fulmer -
Norbert Hartl -
Serge Stinckwich -
Stéphane Ducasse