On Mon, Apr 4, 2011 at 4:58 PM, Mariano Martinez Peck <[hidden email]> wrote: I started to try to release 1.2. Not only I did the list of changes but also: Thanks Mariano. More and more I think we should do the agile way: timeboxing, let's define a fixed planning for Pharo 1.3 beta, rc, and release dates and release whatever happen - even bugs we know - if the bug is still here it means it's not really annoying. And it could always be fixed in 1.3.1 (which should be planned too).
Laurent.
|
In reply to this post by laurent laffont
On Apr 4, 2011, at 4:58 PM, Mariano Martinez Peck wrote: > I started to try to release 1.2. Not only I did the list of changes but also: > > 1) I asked if people still wanted the background: http://forum.world.st/Do-you-want-to-add-the-background-picture-to-the-image-like-we-did-with-Pharo-1-1-td3350726.html#a3355332 > results: negative. So, no backgrund. White as it is now. > > 2) I asked what people wanted that used to be in 1.1: http://forum.world.st/Do-we-want-this-for-Pharo-1-2-and-futures-td3350721.html > guess how many replies? TWO. > results: I would only nclude the installScript. I guess that Hudson could do that very easy, doesn't it ? marcus ? > https://pharo-ic.lille.inria.fr/hudson/job/Pharo%201.2/lastSuccessfulBuild/artifact/Pharo-1.2/Pharo-1.2.st Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD. |
In reply to this post by Marcus Denker-4
>>
>>> Please help because we have not the steam for the splash organization. >> >> So we poor users have to do all the work ?? >> >> Seriously, what is the easiest/fastest way to get to a rough list of the changes between 1.1.1 and 1.2.1 ? >> >> From that list we could try to make a readable list for release notes and then we could try to make a list of bullet points / highlights. >> > > Mariano started a list: I started it :) > > http://code.google.com/p/pharo/wiki/ActionsInPharoOneDotTwo > > All things done should have a tracker entry: > > http://code.google.com/p/pharo/issues/list?can=1&q=milestone=1.2 > http://code.google.com/p/pharo/issues/list?can=1&q=Milestone%3D1.2-DevImage > > > > > > -- > Marcus Denker -- http://www.marcusdenker.de > INRIA Lille -- Nord Europe. Team RMoD. > > |
In reply to this post by Marcus Denker-4
I can go over the scriptloader log and complement what is at http://code.google.com/p/pharo/wiki/ActionsInPharoOneDotTwo
Stef |
In reply to this post by Marcus Denker-4
On Mon, Apr 4, 2011 at 5:33 PM, Marcus Denker <[hidden email]> wrote:
Excellent! and that be included in the zip that hudson creates for the dev images?
-- Mariano http://marianopeck.wordpress.com |
In reply to this post by Marcus Denker-4
On Apr 4, 2011, at 6:36 PM, Mariano Martinez Peck wrote:
It used to be in there. But then people where thinking that it is a startup file that is executed when the image starts up... maybe by renaming it this would get clearer? Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD. |
On Mon, Apr 4, 2011 at 6:46 PM, Marcus Denker <[hidden email]> wrote:
ok, I understand. So yes, or a better name or...... if someone really needs to know that the build script was, then it means: 1) that he is aware of PharoCore / PharoDev 2) That he wants to reproduce the build, or fix a bug, or something. For me, both thins means that such guy is not a beginner/newbie. So we can assume that he also knows where to search such file in hudson ? if true...then we don't include the file... -- Mariano http://marianopeck.wordpress.com |
Free forum by Nabble | Edit this page |