Hi, I recently mentioned issues with the installation of the pharo-launcher on Windows 8.1 Turned out I just needed to download the PharoV30.sources file and place into the installation folder. Now everything seems fine. Is this also a topic for the pharo bug list, or is there another place where I can mention this? Sebastian
there is also an options in settings that downloads and install sources for you automagically. This is the right place to report issues and if you are 100% sure its a bug you can report it also in the pharo fogbuz On Fri, Mar 20, 2015 at 7:04 PM, Sebastian Heidbrink <sheidev@yahoo.de> wrote:
Hi,
I recently mentioned issues with the installation of the pharo-launcher on Windows 8.1
Turned out I just needed to download the PharoV30.sources file and place into the installation folder.
Now everything seems fine.
Is this also a topic for the pharo bug list, or is there another place where I can mention this?
Sebastian
On Fri, Mar 20, 2015 at 7:04 PM, Sebastian Heidbrink <sheidev@yahoo.de> wrote:
Hi,
I recently mentioned issues with the installation of the pharo-launcher on Windows 8.1
Turned out I just needed to download the PharoV30.sources file and place into the installation folder.
Now everything seems fine.
Is this also a topic for the pharo bug list, or is there another place where I can mention this?
Sebastian
On Sat, Mar 21, 2015 at 1:46 AM, kilon alios <kilon.alios@gmail.com> wrote:
there is also an options in settings that downloads and install sources for you automagically.
This is the right place to report issues and if you are 100% sure its a bug you can report it also in the pharo fogbuz
100% is a bit strong and sounds a bit discouraging :). As long as you can list the detailed steps reproduce the problem, then its worth putting in fogbugz. However fogbugz has a lot of old issues and sometimes a new issue is like a lost tree in the forrest. Its generally beneficial if you socialise it on the mail list as well. A good workflow is: 1. Search fogbugz for similar issues. 2. Ask on the mail list if its a known issue, or if you should create a new one. List your steps to reproduce and ideally a solution. 3. Log a new issue on fogbugz, copying the mail list discussion there. Paste the link back to the mail list thread. So in general: * the mail list has a broader audience and gets a better triage * fogbugz tracks history to ensure it doesn't get lost - and nothing happens except what goes through the tracker. (btw, set Project=Launcher) cheers -ben
Bottom line is that reporting a problem in the mailing list first makes much more sense because a) Way more likely to get an answer b) Avoid adding to the list on non existent bugs in fogbugz c) Bring the bug if it really exists to the attention of more people, hence increase that chance of the bug getting a fix. d) Far easier to remind people of the bug later on by just bumping on the thread which everyone on the list will get notified compared to fogbugz that if you are not subscribed to a bug you wont be notified. So yes definitely want to discourage people from starting from fogbugz. Also personally I dont like fogbugz because its so isolated. On Sat, Mar 21, 2015 at 2:15 AM, Ben Coman <btc@openinworld.com> wrote:
On Fri, Mar 20, 2015 at 7:04 PM, Sebastian Heidbrink <sheidev@yahoo.de> wrote:
Hi,
I recently mentioned issues with the installation of the pharo-launcher on Windows 8.1
Turned out I just needed to download the PharoV30.sources file and place into the installation folder.
Now everything seems fine.
Is this also a topic for the pharo bug list, or is there another place where I can mention this?
Sebastian
On Sat, Mar 21, 2015 at 1:46 AM, kilon alios <kilon.alios@gmail.com> wrote:
there is also an options in settings that downloads and install sources for you automagically.
This is the right place to report issues and if you are 100% sure its a bug you can report it also in the pharo fogbuz
100% is a bit strong and sounds a bit discouraging :). As long as you can list the detailed steps reproduce the problem, then its worth putting in fogbugz. However fogbugz has a lot of old issues and sometimes a new issue is like a lost tree in the forrest. Its generally beneficial if you socialise it on the mail list as well.
A good workflow is: 1. Search fogbugz for similar issues. 2. Ask on the mail list if its a known issue, or if you should create a new one. List your steps to reproduce and ideally a solution. 3. Log a new issue on fogbugz, copying the mail list discussion there. Paste the link back to the mail list thread.
So in general: * the mail list has a broader audience and gets a better triage * fogbugz tracks history to ensure it doesn't get lost - and nothing happens except what goes through the tracker. (btw, set Project=Launcher)
cheers -ben
I think that we should have a Pharo-bugs mailing list that gets notified for each bug that is filled in fogbugz 2015-03-21 4:54 GMT-03:00 kilon alios <kilon.alios@gmail.com>:
Bottom line is that reporting a problem in the mailing list first makes much more sense because
a) Way more likely to get an answer b) Avoid adding to the list on non existent bugs in fogbugz c) Bring the bug if it really exists to the attention of more people, hence increase that chance of the bug getting a fix. d) Far easier to remind people of the bug later on by just bumping on the thread which everyone on the list will get notified compared to fogbugz that if you are not subscribed to a bug you wont be notified.
So yes definitely want to discourage people from starting from fogbugz. Also personally I dont like fogbugz because its so isolated.
On Sat, Mar 21, 2015 at 2:15 AM, Ben Coman <btc@openinworld.com> wrote:
On Fri, Mar 20, 2015 at 7:04 PM, Sebastian Heidbrink <sheidev@yahoo.de> wrote:
Hi,
I recently mentioned issues with the installation of the pharo-launcher on Windows 8.1
Turned out I just needed to download the PharoV30.sources file and place into the installation folder.
Now everything seems fine.
Is this also a topic for the pharo bug list, or is there another place where I can mention this?
Sebastian
On Sat, Mar 21, 2015 at 1:46 AM, kilon alios <kilon.alios@gmail.com> wrote:
there is also an options in settings that downloads and install sources for you automagically.
This is the right place to report issues and if you are 100% sure its a bug you can report it also in the pharo fogbuz
100% is a bit strong and sounds a bit discouraging :). As long as you can list the detailed steps reproduce the problem, then its worth putting in fogbugz. However fogbugz has a lot of old issues and sometimes a new issue is like a lost tree in the forrest. Its generally beneficial if you socialise it on the mail list as well.
A good workflow is: 1. Search fogbugz for similar issues. 2. Ask on the mail list if its a known issue, or if you should create a new one. List your steps to reproduce and ideally a solution. 3. Log a new issue on fogbugz, copying the mail list discussion there. Paste the link back to the mail list thread.
So in general: * the mail list has a broader audience and gets a better triage * fogbugz tracks history to ensure it doesn't get lost - and nothing happens except what goes through the tracker. (btw, set Project=Launcher)
cheers -ben
Nice idea!
I think that we should have a Pharo-bugs mailing list that gets notified for each bug that is filled in fogbugz
2015-03-21 4:54 GMT-03:00 kilon alios <kilon.alios@gmail.com <mailto:kilon.alios@gmail.com>>:
Bottom line is that reporting a problem in the mailing list first makes much more sense because
a) Way more likely to get an answer b) Avoid adding to the list on non existent bugs in fogbugz c) Bring the bug if it really exists to the attention of more people, hence increase that chance of the bug getting a fix. d) Far easier to remind people of the bug later on by just bumping on the thread which everyone on the list will get notified compared to fogbugz that if you are not subscribed to a bug you wont be notified.
So yes definitely want to discourage people from starting from fogbugz. Also personally I dont like fogbugz because its so isolated.
On Sat, Mar 21, 2015 at 2:15 AM, Ben Coman <btc@openinworld.com <mailto:btc@openinworld.com>> wrote:
On Fri, Mar 20, 2015 at 7:04 PM, Sebastian Heidbrink <sheidev@yahoo.de <mailto:sheidev@yahoo.de>> wrote:
Hi,
I recently mentioned issues with the installation of the pharo-launcher on Windows 8.1
Turned out I just needed to download the PharoV30.sources file and place into the installation folder.
Now everything seems fine.
Is this also a topic for the pharo bug list, or is there another place where I can mention this?
Sebastian
On Sat, Mar 21, 2015 at 1:46 AM, kilon alios <kilon.alios@gmail.com <mailto:kilon.alios@gmail.com>> wrote:
there is also an options in settings that downloads and install sources for you automagically.
This is the right place to report issues and if you are 100% sure its a bug you can report it also in the pharo fogbuz
100% is a bit strong and sounds a bit discouraging :). As long as you can list the detailed steps reproduce the problem, then its worth putting in fogbugz. However fogbugz has a lot of old issues and sometimes a new issue is like a lost tree in the forrest. Its generally beneficial if you socialise it on the mail list as well.
A good workflow is: 1. Search fogbugz for similar issues. 2. Ask on the mail list if its a known issue, or if you should create a new one. List your steps to reproduce and ideally a solution. 3. Log a new issue on fogbugz, copying the mail list discussion there. Paste the link back to the mail list thread.
So in general: * the mail list has a broader audience and gets a better triage * fogbugz tracks history to ensure it doesn't get lost - and nothing happens except what goes through the tracker. (btw, set Project=Launcher)
cheers -ben
Le 21/03/2015 14:08, stepharo a écrit :
Nice idea!
I think that we should have a Pharo-bugs mailing list that gets notified for each bug that is filled in fogbugz
Yes that would be nice, when you look at bugs on fogbugz site, you do not always see that it is discussed in the list (lot of threads) -- Regards, Alain
On Sat, Mar 21, 2015 at 9:55 PM, Alain Rastoul <alf.mmm.cat@gmail.com> wrote:
Le 21/03/2015 14:08, stepharo a écrit :
Nice idea!
I think that we should have a Pharo-bugs mailing list that gets notified for each bug that is filled in fogbugz
Yes that would be nice, when you look at bugs on fogbugz site, you do not always see that it is discussed in the list (lot of threads)
It would be nice, but btw will not address that situation. Parties interested in the issue woudl still need to copy mail list discussion there, or link to the mail archive of the discussion. Fogbugz should hold case history. cheers -ben
Le 22/03/2015 03:36, Ben Coman a écrit :
It would be nice, but btw will not address that situation. Parties interested in the issue woudl still need to copy mail list discussion there, or link to the mail archive of the discussion. Fogbugz should hold case history. cheers -ben
You are right if you see the discussion in the list. I recently added a note to a case without seeing it was discussed in the list and think it was not the good place. A separate list for bugs (threads in the list do not allways clearly link to the bugs and they are lot of various threads) may have helped. With a tag in the title in case of opened bugs. I agree that fogbugz should hold the history. -- Regards, Alain
I confirm that this problem is even on Windows 7. I does not start without PharoV30.sources. Any option in settings is not solution in this case, because to get into settings, you have to open it first, which is not possible. Another thing is that in my opinion pharo launcher is not "advertised" enough. I mean it is so great tool it should be directly downloadable from http://pharo.org/ ... right now, I had a problem to find a download link for windows even with google. Jan kilon.alios wrote
there is also an options in settings that downloads and install sources for you automagically.
This is the right place to report issues and if you are 100% sure its a bug you can report it also in the pharo fogbuz
On Fri, Mar 20, 2015 at 7:04 PM, Sebastian Heidbrink <
sheidev@
> wrote:
Hi,
I recently mentioned issues with the installation of the pharo-launcher on Windows 8.1
Turned out I just needed to download the PharoV30.sources file and place into the installation folder.
Now everything seems fine.
Is this also a topic for the pharo bug list, or is there another place where I can mention this?
Sebastian
-- View this message in context: http://forum.world.st/Pharo-Launcher-Windows-8-1-tp4813640p4813978.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.
participants (7)
-
Alain Rastoul -
Ben Coman -
Jan B. -
kilon alios -
Ronie Salgado -
Sebastian Heidbrink -
stepharo