[Pharo-project] Pharo 1.0 release plan
Hi everyone, Last week in Bern, Marcus, Stef, and I have been discussing a plan for a first release of Pharo. Overall, the goal is to produce a valuable, stable "product" within reasonable time. Is there anything important we missed? Any suggestions? FUNCTIONAL REQUIREMENTS -------------------------------------------- Integrate Polymorph Integrate TrueType Main EToys removal Refactor Traits API NON-FUNCTIONAL REQUIREMENTS -------------------------------------------- All tests green License clean (check OLPC changes) First consistent version of the website (work in progress) INFRASTRUCTURE -------------------------------------------- Increase efficiency of producing new updates (work in progress) Prepare second update stream to maintain released version TENTATIVE SCHEDULE -------------------------------------------- Going beta in January Release of version 1.0 in February Cheers, Adrian ___________________ http://www.adrian-lienhard.ch/
On Sun, Nov 2, 2008 at 1:02 PM, Adrian Lienhard <adi@netstyle.ch> wrote:
Is there anything important we missed? Any suggestions?
- review pharo-dev images and make comments so that the official Pharo image contains some dev tools and pharo-dev becomes useless. -- 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)
thanks, I forgot to list the one-click image. I added the plan to http://code.google.com/p/pharo/wiki/Milestones Concerning terminology, I suggest to name the official Pharo image, which will be packaged as a one-click image, "Pharo-IDE". And the one where the actual development of Pharo takes place is named Pharo-CORE. Using DEV is ambiguous because its not clear whether this image is supposed to develop applications or Pharo itself. Adrian On Nov 3, 2008, at 10:15 , Damien Cassou wrote:
On Sun, Nov 2, 2008 at 1:02 PM, Adrian Lienhard <adi@netstyle.ch> wrote:
Is there anything important we missed? Any suggestions?
- review pharo-dev images and make comments so that the official Pharo image contains some dev tools and pharo-dev becomes useless.
-- 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
2008/11/3 Adrian Lienhard <adi@netstyle.ch>:
thanks, I forgot to list the one-click image. I added the plan to http://code.google.com/p/pharo/wiki/Milestones
Concerning terminology, I suggest to name the official Pharo image, which will be packaged as a one-click image, "Pharo-IDE". And the one where the actual development of Pharo takes place is named Pharo-CORE. Using DEV is ambiguous because its not clear whether this image is supposed to develop applications or Pharo itself.
Yes good idea, to have 2 differents names, but why Pharo-IDE ? There is no IDE in the core version ? Why not Pharo-stable and Pharo-unstable ? -- Serge Stinckwich IRD - UR 079 Geodes, MSI Team, Hanoi, Vietnam Smalltalkers do: [:it | All with: Class, (And love: it)] http://doesnotunderstand.org/
On 03.11.2008, at 10:55, Serge Stinckwich wrote:
2008/11/3 Adrian Lienhard <adi@netstyle.ch>:
thanks, I forgot to list the one-click image. I added the plan to http://code.google.com/p/pharo/wiki/Milestones
Concerning terminology, I suggest to name the official Pharo image, which will be packaged as a one-click image, "Pharo-IDE". And the one where the actual development of Pharo takes place is named Pharo-CORE. Using DEV is ambiguous because its not clear whether this image is supposed to develop applications or Pharo itself.
Yes good idea, to have 2 differents names, but why Pharo-IDE ? There is no IDE in the core version ? Why not Pharo-stable and Pharo-unstable ?
It's not the stability that distinguishes the two. The CORE does not have Omnibrower and RB and things like that. Marcus -- Marcus Denker -- denker@iam.unibe.ch http://www.iam.unibe.ch/~denker
I suggest to have at least one next image - without everything what can be safely unloaded. For the next cleaning and shrinking purposes. Of course if you want to have similar sequence of automatically build images like the KernelImage. -- Pavel On Mon, Nov 3, 2008 at 10:49 AM, Adrian Lienhard <adi@netstyle.ch> wrote:
thanks, I forgot to list the one-click image. I added the plan to http://code.google.com/p/pharo/wiki/Milestones
Concerning terminology, I suggest to name the official Pharo image, which will be packaged as a one-click image, "Pharo-IDE". And the one where the actual development of Pharo takes place is named Pharo-CORE. Using DEV is ambiguous because its not clear whether this image is supposed to develop applications or Pharo itself.
Adrian
On Nov 3, 2008, at 10:15 , Damien Cassou wrote:
On Sun, Nov 2, 2008 at 1:02 PM, Adrian Lienhard <adi@netstyle.ch> wrote:
Is there anything important we missed? Any suggestions?
- review pharo-dev images and make comments so that the official Pharo image contains some dev tools and pharo-dev becomes useless.
-- 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 Nov 3, 2008, at 10:55 , Serge Stinckwich wrote:
2008/11/3 Adrian Lienhard <adi@netstyle.ch>:
thanks, I forgot to list the one-click image. I added the plan to http://code.google.com/p/pharo/wiki/Milestones
Concerning terminology, I suggest to name the official Pharo image, which will be packaged as a one-click image, "Pharo-IDE". And the one where the actual development of Pharo takes place is named Pharo-CORE. Using DEV is ambiguous because its not clear whether this image is supposed to develop applications or Pharo itself.
Yes good idea, to have 2 differents names, but why Pharo-IDE ? There is no IDE in the core version ?
There is only a minimal one, and it will be further reduced in the future. So, for real work, it is suggested to use the "IDE" image, which includes all the productivity tools like autocompletion and syntax highlighting (for a list see http://code.google.com/p/pharo/wiki/Packages) . However, for a Seaside server I would rather use the core to reduce the memory footprint.
Why not Pharo-stable and Pharo-unstable ?
because there exists a stable CORE too. Changes are done on the core and from this the IDE is then built. I hope this helps to explain the rationale behind the suggested naming. Adrian
Hi Adrian, Adrian Lienhard wrote:
Concerning terminology, I suggest to name the official Pharo image, which will be packaged as a one-click image, "Pharo-IDE". And the one where the actual development of Pharo takes place is named Pharo-CORE. Using DEV is ambiguous because its not clear whether this image is supposed to develop applications or Pharo itself.
I'm also not happy with Pharo-IDE name. I'd rather stay with DEV, because we all were getting used of the name from Damien's images. I also don't find the name ambiguous, it means the images as a TOOL for development, for developers. While CORE means some core image on top of which you can then build your own image, according to your own wishes, without removing unneeded stuff first. Best regards Janko -- Janko Mivšek AIDA/Web Smalltalk Web Application Server http://www.aidaweb.si
On Mon, Nov 3, 2008 at 10:49 AM, Adrian Lienhard <adi@netstyle.ch> wrote:
Concerning terminology, I suggest to name the official Pharo image, which will be packaged as a one-click image, "Pharo-IDE". And the one where the actual development of Pharo takes place is named Pharo-CORE. Using DEV is ambiguous because its not clear whether this image is supposed to develop applications or Pharo itself.
During ESUG, we discussed about that with Marcus. IIRC, he wanted the current pharo-dev (your Pharo-IDE) to be named just Pharo. The core, which should only be used by people "knowing what they do" would be named Pharo-core. -- 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)
Yes good idea, to have 2 differents names, but why Pharo-IDE ? There is no IDE in the core version ?
There is only a minimal one, and it will be further reduced in the future. So, for real work, it is suggested to use the "IDE" image, which includes all the productivity tools like autocompletion and syntax highlighting (for a list see http://code.google.com/p/pharo/wiki/Packages) . However, for a Seaside server I would rather use the core to reduce the memory footprint.
I tend to agree with Serge on this. Having IDE in the name might be confusing for people. Why not to have Pharo-standard and Pharo-Enterprise ? Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
On 03.11.2008, at 15:44, Alexandre Bergel wrote:
Yes good idea, to have 2 differents names, but why Pharo-IDE ? There is no IDE in the core version ?
There is only a minimal one, and it will be further reduced in the future. So, for real work, it is suggested to use the "IDE" image, which includes all the productivity tools like autocompletion and syntax highlighting (for a list see http://code.google.com/p/pharo/wiki/Packages) . However, for a Seaside server I would rather use the core to reduce the memory footprint.
I tend to agree with Serge on this. Having IDE in the name might be confusing for people. Why not to have Pharo-standard and Pharo-Enterprise ?
The idea is that the version *with* the tools is the standard. Not the one without. ;-) Marcus -- Marcus Denker -- denker@iam.unibe.ch http://www.iam.unibe.ch/~denker
Why not to have Pharo-standard and Pharo-Enterprise ?
The idea is that the version *with* the tools is the standard. Not the one without. ;-)
What about Pharo-minimal and Pharo-enterprise? Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
On 03.11.2008, at 15:52, Alexandre Bergel wrote:
Why not to have Pharo-standard and Pharo-Enterprise ?
The idea is that the version *with* the tools is the standard. Not the one without. ;-)
What about Pharo-minimal and Pharo-enterprise?
I vote for Pharo-Core and Pharo. Marcus -- Marcus Denker -- denker@iam.unibe.ch http://www.iam.unibe.ch/~denker
During ESUG, we discussed about that with Marcus. IIRC, he wanted the current pharo-dev (your Pharo-IDE) to be named just Pharo. The core, which should only be used by people "knowing what they do" would be named Pharo-core.
I agree, in my humble opinion it seems to be the best choice. Francois ps: I'm new to the list. Keep the good work with pharo guys!
On Mon, Nov 3, 2008 at 3:55 PM, Marcus Denker <denker@iam.unibe.ch> wrote:
I vote for Pharo-Core and Pharo.
So do I -- 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)
Marcus Denker wrote:
I vote for Pharo-Core and Pharo.
+0.9
Pharo-Core and Pharo-Dev (+0.1)
Michael
Ditto, I like Core and Dev better, but Pharo-Core and Pharo aren't bad either. Ramon Leon http://onsmalltalk.com
ok, then, let's take Pharo-Core and Pharo. Adrian On Nov 3, 2008, at 17:07 , Ramon Leon wrote:
Marcus Denker wrote:
I vote for Pharo-Core and Pharo.
+0.9
Pharo-Core and Pharo-Dev (+0.1)
Michael
Ditto, I like Core and Dev better, but Pharo-Core and Pharo aren't bad either.
Ramon Leon http://onsmalltalk.com
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Adrian Lienhard ha scritto:
On Nov 3, 2008, at 10:55 , Serge Stinckwich wrote:
Why not Pharo-stable and Pharo-unstable ?
because there exists a stable CORE too. Changes are done on the core and from this the IDE is then built.
I hope this helps to explain the rationale behind the suggested naming.
A non-Smalltalker who reads Pharo-IDE will assume this is the IDE only, and not the CORE+the dev tools. Why not something like Pharo-SDK? Giovanni
2008/11/3 Adrian Lienhard <adi@netstyle.ch>:
ok, then, let's take Pharo-Core and Pharo.
+1 -- Serge Stinckwich IRD - UR 079 Geodes, MSI Team, Hanoi, Vietnam Smalltalkers do: [:it | All with: Class, (And love: it)] http://doesnotunderstand.org/
On Mon, Nov 3, 2008 at 3:55 PM, Marcus Denker <denker@iam.unibe.ch> wrote:
I vote for Pharo-Core and Pharo.
+1 also, can we have the bike shed in blue ? -- Damien Pollet type less, do more [ | ] http://people.untyped.org/damien.pollet
Hi Adrian, how about some getting started information - inside the image and on a web page? What would be useful for beginners? Cheers Matthias On Sun, Nov 2, 2008 at 1:02 PM, Adrian Lienhard <adi@netstyle.ch> wrote:
Hi everyone,
Last week in Bern, Marcus, Stef, and I have been discussing a plan for a first release of Pharo. Overall, the goal is to produce a valuable, stable "product" within reasonable time. Is there anything important we missed? Any suggestions?
FUNCTIONAL REQUIREMENTS -------------------------------------------- Integrate Polymorph Integrate TrueType Main EToys removal Refactor Traits API
NON-FUNCTIONAL REQUIREMENTS -------------------------------------------- All tests green License clean (check OLPC changes) First consistent version of the website (work in progress)
INFRASTRUCTURE -------------------------------------------- Increase efficiency of producing new updates (work in progress) Prepare second update stream to maintain released version
TENTATIVE SCHEDULE -------------------------------------------- Going beta in January Release of version 1.0 in February
Cheers, Adrian ___________________ http://www.adrian-lienhard.ch/
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Hi Matthias, yes, that would be very useful (I added it to the wiki)! Can you help with this? Cheers, Adrian On Nov 4, 2008, at 12:52 , Matthias Berth wrote:
Hi Adrian,
how about some getting started information - inside the image and on a web page? What would be useful for beginners?
Cheers
Matthias
On Sun, Nov 2, 2008 at 1:02 PM, Adrian Lienhard <adi@netstyle.ch> wrote:
Hi everyone,
Last week in Bern, Marcus, Stef, and I have been discussing a plan for a first release of Pharo. Overall, the goal is to produce a valuable, stable "product" within reasonable time. Is there anything important we missed? Any suggestions?
FUNCTIONAL REQUIREMENTS -------------------------------------------- Integrate Polymorph Integrate TrueType Main EToys removal Refactor Traits API
NON-FUNCTIONAL REQUIREMENTS -------------------------------------------- All tests green License clean (check OLPC changes) First consistent version of the website (work in progress)
INFRASTRUCTURE -------------------------------------------- Increase efficiency of producing new updates (work in progress) Prepare second update stream to maintain released version
TENTATIVE SCHEDULE -------------------------------------------- Going beta in January Release of version 1.0 in February
Cheers, Adrian ___________________ http://www.adrian-lienhard.ch/
_______________________________________________ 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
What about having short screencasts that show basic steps such as class and method creation, using the debugger,... I have SnapZPro, I could make up some Cheers, Alexandre On 4 Nov 2008, at 10:38, Adrian Lienhard wrote:
Hi Matthias,
yes, that would be very useful (I added it to the wiki)! Can you help with this?
Cheers, Adrian
On Nov 4, 2008, at 12:52 , Matthias Berth wrote:
Hi Adrian,
how about some getting started information - inside the image and on a web page? What would be useful for beginners?
Cheers
Matthias
On Sun, Nov 2, 2008 at 1:02 PM, Adrian Lienhard <adi@netstyle.ch> wrote:
Hi everyone,
Last week in Bern, Marcus, Stef, and I have been discussing a plan for a first release of Pharo. Overall, the goal is to produce a valuable, stable "product" within reasonable time. Is there anything important we missed? Any suggestions?
FUNCTIONAL REQUIREMENTS -------------------------------------------- Integrate Polymorph Integrate TrueType Main EToys removal Refactor Traits API
NON-FUNCTIONAL REQUIREMENTS -------------------------------------------- All tests green License clean (check OLPC changes) First consistent version of the website (work in progress)
INFRASTRUCTURE -------------------------------------------- Increase efficiency of producing new updates (work in progress) Prepare second update stream to maintain released version
TENTATIVE SCHEDULE -------------------------------------------- Going beta in January Release of version 1.0 in February
Cheers, Adrian ___________________ http://www.adrian-lienhard.ch/
_______________________________________________ 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
-- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
sure, that would be nice. However, I would wait until a bit later when we have Polymorph + TT. Adrian On Nov 4, 2008, at 18:05 , Alexandre Bergel wrote:
What about having short screencasts that show basic steps such as class and method creation, using the debugger,...
I have SnapZPro, I could make up some
Cheers, Alexandre
On 4 Nov 2008, at 10:38, Adrian Lienhard wrote:
Hi Matthias,
yes, that would be very useful (I added it to the wiki)! Can you help with this?
Cheers, Adrian
On Nov 4, 2008, at 12:52 , Matthias Berth wrote:
Hi Adrian,
how about some getting started information - inside the image and on a web page? What would be useful for beginners?
Cheers
Matthias
On Sun, Nov 2, 2008 at 1:02 PM, Adrian Lienhard <adi@netstyle.ch> wrote:
Hi everyone,
Last week in Bern, Marcus, Stef, and I have been discussing a plan for a first release of Pharo. Overall, the goal is to produce a valuable, stable "product" within reasonable time. Is there anything important we missed? Any suggestions?
FUNCTIONAL REQUIREMENTS -------------------------------------------- Integrate Polymorph Integrate TrueType Main EToys removal Refactor Traits API
NON-FUNCTIONAL REQUIREMENTS -------------------------------------------- All tests green License clean (check OLPC changes) First consistent version of the website (work in progress)
INFRASTRUCTURE -------------------------------------------- Increase efficiency of producing new updates (work in progress) Prepare second update stream to maintain released version
TENTATIVE SCHEDULE -------------------------------------------- Going beta in January Release of version 1.0 in February
Cheers, Adrian ___________________ http://www.adrian-lienhard.ch/
_______________________________________________ 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
-- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
sure, that would be nice. However, I would wait until a bit later when we have Polymorph + TT.
Make sense yes. Alexandre
On Nov 4, 2008, at 18:05 , Alexandre Bergel wrote:
What about having short screencasts that show basic steps such as class and method creation, using the debugger,...
I have SnapZPro, I could make up some
Cheers, Alexandre
On 4 Nov 2008, at 10:38, Adrian Lienhard wrote:
Hi Matthias,
yes, that would be very useful (I added it to the wiki)! Can you help with this?
Cheers, Adrian
On Nov 4, 2008, at 12:52 , Matthias Berth wrote:
Hi Adrian,
how about some getting started information - inside the image and on a web page? What would be useful for beginners?
Cheers
Matthias
On Sun, Nov 2, 2008 at 1:02 PM, Adrian Lienhard <adi@netstyle.ch> wrote:
Hi everyone,
Last week in Bern, Marcus, Stef, and I have been discussing a plan for a first release of Pharo. Overall, the goal is to produce a valuable, stable "product" within reasonable time. Is there anything important we missed? Any suggestions?
FUNCTIONAL REQUIREMENTS -------------------------------------------- Integrate Polymorph Integrate TrueType Main EToys removal Refactor Traits API
NON-FUNCTIONAL REQUIREMENTS -------------------------------------------- All tests green License clean (check OLPC changes) First consistent version of the website (work in progress)
INFRASTRUCTURE -------------------------------------------- Increase efficiency of producing new updates (work in progress) Prepare second update stream to maintain released version
TENTATIVE SCHEDULE -------------------------------------------- Going beta in January Release of version 1.0 in February
Cheers, Adrian ___________________ http://www.adrian-lienhard.ch/
_______________________________________________ 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
-- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
_______________________________________________ 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
-- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Since a 1.0 release is likely to get attention, maybe would be wise to integrate Polymorph+TT beforehand? On Tue, Nov 4, 2008 at 11:36 AM, Alexandre Bergel <alexandre@bergel.eu> wrote:
sure, that would be nice. However, I would wait until a bit later when we have Polymorph + TT.
Make sense yes.
Alexandre
On Nov 4, 2008, at 18:05 , Alexandre Bergel wrote:
What about having short screencasts that show basic steps such as class and method creation, using the debugger,...
I have SnapZPro, I could make up some
Cheers, Alexandre
On 4 Nov 2008, at 10:38, Adrian Lienhard wrote:
Hi Matthias,
yes, that would be very useful (I added it to the wiki)! Can you help with this?
Cheers, Adrian
On Nov 4, 2008, at 12:52 , Matthias Berth wrote:
Hi Adrian,
how about some getting started information - inside the image and on a web page? What would be useful for beginners?
Cheers
Matthias
On Sun, Nov 2, 2008 at 1:02 PM, Adrian Lienhard <adi@netstyle.ch> wrote:
Hi everyone,
Last week in Bern, Marcus, Stef, and I have been discussing a plan for a first release of Pharo. Overall, the goal is to produce a valuable, stable "product" within reasonable time. Is there anything important we missed? Any suggestions?
FUNCTIONAL REQUIREMENTS -------------------------------------------- Integrate Polymorph Integrate TrueType Main EToys removal Refactor Traits API
NON-FUNCTIONAL REQUIREMENTS -------------------------------------------- All tests green License clean (check OLPC changes) First consistent version of the website (work in progress)
INFRASTRUCTURE -------------------------------------------- Increase efficiency of producing new updates (work in progress) Prepare second update stream to maintain released version
TENTATIVE SCHEDULE -------------------------------------------- Going beta in January Release of version 1.0 in February
Cheers, Adrian ___________________ http://www.adrian-lienhard.ch/
_______________________________________________ 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
-- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
_______________________________________________ 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
-- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
On Tue, Nov 4, 2008 at 7:37 PM, David Mitchell <david.mitchell@gmail.com> wrote:
Since a 1.0 release is likely to get attention, maybe would be wise to integrate Polymorph+TT beforehand?
Look at the very first message in this thread or at http://code.google.com/p/pharo/wiki/Milestones. -- 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)
participants (16)
-
Adrian Lienhard -
Alexandre Bergel -
Damien Cassou -
Damien Pollet -
Dan Corneanu -
David Mitchell -
Francois Stephany -
Giovanni Corriga -
Janko Mivšek -
Marcus Denker -
Matthias Berth -
Michael Rueger -
Pavel Krivanek -
Ramon Leon -
Serge Stinckwich -
Tudor Girba