you can use the google interface to get access to what is closed in 1.1 Stef On Dec 1, 2009, at 11:03 AM, Tim Mackinnon wrote:
Actually I am thinking of something like the following (this is JBoss - they use Jira - which is free for open source projects, although I find it a bit clunky - but it gives an idea. I have actually seen Trac - the wiki and ticket system used very effectively);
This link shows all of their version for the JBoss Web project: https://jira.jboss.org/jira/browse/JBWEB?report=com.atlassian.jira.plugin.sy...
This link shows what was fixed in 2.1.1 GA https://jira.jboss.org/jira/browse/JBWEB/fixforversion/12312592
I guess I am thinking that when I see the following in this list (from Marcus) - this information should appear somewhere as the things that were fixed in 9.11.5? 11066 -----
Issue 1526: remove #addInstanceVarNamed:withValue: Issue 1518: #abbreviatedBrowserButtons should be removed Issue 476: [Pending Etoy Cleaning] Object>>knownName Issue 1520: remove global References
Tim
On 30 Nov 2009, at 22:34, Michael Roberts wrote:
do you mean the svn thing? you can mark files in the repository in a way that updates the issue tracker. I haven't tried it (we have no files) but the docs look straightforward. It's meant for projects that actually keep their source in the repository, but I think we could have a dummy file that acted the same way. It would be a logical closure for each issue to mark it with the update. That way it is external to the image and gives the full life cycle on the tracker which I think would be useful.
cheers Mike
On Mon, Nov 30, 2009 at 11:03 PM, Stéphane Ducasse <stephane.ducasse@inria.fr> wrote:
I do not get it? Can you explain how this works? Because right now you take ScriptLoader and you get the log of all the issue that have been integrated.
Stef
On Nov 30, 2009, at 10:48 PM, Michael Roberts wrote:
you can check the log of the script loader. I don't have the code to hand but check the state of the singleton I think.
It might be nice in the future to use the google SVN feature to tag issues with the image update as we close them.
cheers, Mike
On Mon, Nov 30, 2009 at 10:24 PM, Tim Mackinnon <tamackinnon@gmail.com> wrote:
Hi guys - I noticed there was a new 9.11.4 release since buenos aires - and I got to wondering what issues have been resolved in it (as I am trying to follow Pharo by example - I am trying to test out features to see if they work as I progress through the material).
Anyway - is there a list of issues fixed marked against each new version? I can see the list at: http://code.google.com/p/pharo/issues/list# - but it doesn't list any build numbers - just milestone 1.1?
Tim _______________________________________________ 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
_______________________________________________ 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