Mariano Martinez Peck wrote:
On Mon, Dec 21, 2009 at 9:48 PM, Stan Shepherd <stan.shepherd414@gmail.com>wrote:
Mariano Martinez Peck wrote:
As already said several times. For me, we have to:
1) Put ALL our effort and or priority to release the 1.0 stable. This means, try to fix the 1.0 opened fixes.
What is the suggested workflow for those of us who want to work off the stable version, and feedback where we find outstanding issues? I would expect to try out the offending code in a 'patched up to date' version of 1.0, to see if it is reproducable there, in which case a search of open bug reports, and possibly a new bug report, would be in order. Is there an easy way to maintain such an up to date version 1.0, with harvested bug fixes?
In my opinion, it is easy. If you are a Pharo developer you might want to use 1.1 and code there. If you are just a "user" of pharo, use the 1.0. If there are bugs, just report them following this: http://www.pharo-project.org/community/issue-tracking
And then we see. If the bug is a "1.0 issue" we will try to fix it and integrated. Maybe it is 1.1. But it doesn't care. You should use 1.0 for your applications and report anything you want (issue, feedback, whatever) regardless 1.1 (do as if 1.1 doesn't exist).
Cheers
Mariano
...Stan
Hi Mariano, I suppose my question was mainly about how to keep that 1.0 version up with its current fixes. Is it a question of watching out for a new release on the downloads page. It would be preferable to pick up all updates (semi)automatically, in which case you know that a bug you hit is still a bug. I know I have seen bugs such as the one I just logged, but felt they were likely already in the works, or caused by something I'd done. If I can easily keep an image as the 'gold standard' of where a patched up to date image should be, I'm more likely to decide something really is a bug and log it. Cheeers, ...Stan -- View this message in context: http://n2.nabble.com/Re-did-you-check-in-1-1-how-the-old-browser-now-support... Sent from the Pharo Smalltalk mailing list archive at Nabble.com.