now can we get a working keyboard? On Wednesday, August 7, 2013, Igor Stasenko <[email protected]> wrote: > Agree with everything you said. > As i said, my impression was that Guille pushed unfininowshed/incomplete pieces. > And that is what i against. > Because if we go that way, then someone will start pushing changes > which even don't compile. > > I hope i made my point clear, what blessed means. It is not synonym > to 'stable'. > > > On 7 August 2013 17:11, Esteban Lorenzano <[email protected]> wrote: >> IMO is no point on ask for keeping an "all-time-stable" VM in the development process (it is even a contradiction). >> Is the same as asking for a 3.0 stable before release (yes, is the same... we are trying to have same process for both). >> >> VM development is not stable right now, same way it is not stable 3.0 >> Want stable stuff? you need to take the stable VM and Pharo 2.0 (even with the bugs we all know). >> Ok, we (the pharo developers community) cannot do that, we need to work on the bleeding edge and because of that, some times we get uncomfortable situations. >> But then we all know how hard is to have a functionality working properly and well tested. Our only way to do that is to put it in the development trunk and ask for feedback. >> >> So... yes, I'm sorry it annoys some time to time, but latest-VM will have periods in which it doesn't work as expected... is the only way this small community can advance: Developers introduce a functionality, community tests and provide feedback, then loop. >> >> Now, what we should have is a better way of mark stuff.. so we can backport stuff et all. >> For that, what we should have is: >> - all sources in just one repository, including vmmaker (I'm working on that) >> - create a tag (that we can branch and backport stuff) each release. >> >> no need to stress about :) >> >> my 2c >> >> Esteban >> >> >> On Aug 7, 2013, at 4:43 PM, Igor Stasenko <[email protected]> wrote: >> >>> On 7 August 2013 15:55, Guillermo Polito <[email protected]> wrote: >>>> >>>> On Wed, Aug 7, 2013 at 2:41 PM, Igor Stasenko <[email protected]> wrote: >>>>> >>>>> My understanding how it should be: >>>>> - you work in own branch (and in git, repository clone is already a >>>>> branch, just on your computer). >>>>> If you want to make it public you need to make own branch on gitorious >>>>> and commit there. >>>>> - once you finished with changes and tested it , you are free to merge >>>>> with blessed >>>>> (no need to have GODs permission to do that, or make pull requests) >>>> >>>> >>>> We did all that. We tested it with Ben because he needed the change to send >>>> ctrl events from the vm to the image, which were not sent. We tested in our >>>> computers, and we had no much trouble. >>>> >>>> - I do not use delete key because I don't have one >>>> - circumflex accent (return) was working with my keyboard layout >>>> >>>> So the vm was to me in a completely usable state. >>>> >>>>> >>>>> >>>>> now i understand we are humans and not immune to mistakes, but i >>>>> insist that committing to blessed >>>> >>>> >>>> 'blessed' is a crappy name for a repository. And the idea that the code in >>>> this repository is always working flawlessly is nonsense. For example, we >>>> had for months the problem with the smallinteger in there. >>>> >>>> And then, the unstable is in another repository then? Where is that >>>> repository? Why do we have to make another repository for that and not just >>>> a branch (in the same repo, not in my machine)? >>>> >>> >>> so what you proposing? lets everyone put own unfinished changes into >>> same repository >>> without synchronization and see how it flies? >>> it won't fly, i can tell you even without trying. >>> >>>>> >>>>> should be done after some manual testing and checking it don't breaks >>>>> things badly, and of course >>>>> blessed is not for committing the unfinished code , which in the >>>>> middle of work. >>>> >>>> >>>> First, we considered it as finished. What you found was a bug, not a pending >>>> to do task. >>>> >>> >>> Ah, in that case it is perfectly ok then. >>> It is your messages in previous mails gave me impression that
-- --- Philippe Back Dramatic Performance Improvements Mob: +32(0) 478 650 140 | Fax: +32 (0) 70 408 027 Mail:[email protected] | Web: http://philippeback.eu Blog: http://philippeback.be | Twitter: @philippeback Youtube: http://www.youtube.com/user/philippeback/videos High Octane SPRL rue cour Boisacq 101 | 1301 Bierges | Belgium Featured on the Software Process and Measurement Cast http://spamcast.libsyn.com Sparx Systems Enterprise Architect and Ability Engineering EADocX Value Added Reseller
