Tim Mackinnon | 1 Dec 2009 11:03
Picon

Re: How do I know which issues are resolved in each new release?

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.system.project:versions-panel

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
(Continue reading)

Stéphane Ducasse | 1 Dec 2009 16:10
Picon
Picon
Favicon
Gravatar

Re: How do I know which issues are resolved in each new release?

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.system.project:versions-panel
> 
> 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:
(Continue reading)

Stéphane Ducasse | 1 Dec 2009 16:10
Picon
Picon
Favicon
Gravatar

Re: How do I know which issues are resolved in each new release?

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.system.project:versions-panel
> 
> 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:
(Continue reading)


Gmane