change log link for releases

[GoogleCodeExporter]

All the issues that have been resolved since the 1.1 release should be marked 
with milestone 1.1.  When we release 1.2 there should be a change log notice 
which includes a link to the issues page showing all the issues with milestone 
1.2.  

All future issues that are resolved should be assigned to a milestone 
corresponding to the cleartk-release version that it will go with.  This needs 
to be documented somewhere...

Original issue reported on code.google.com by phi...@ogren.info on 4 Aug 2012 at 3:55

[GoogleCodeExporter]

Original comment by phi...@ogren.info on 4 Aug 2012 at 6:05

[GoogleCodeExporter]

I've gone through all the tickets that have been closed since the last (1.1) 
release and marked them as appropriate. Here's the link for the issues we've 
closed for the next (1.2) release:

https://code.google.com/p/cleartk/issues/list?can=1&q=Milestone%3D1.2+status%3AF
ixed+OR+status%3ADone

Probably we should also go back and tag the things that were closed in the 1.1 
release...

Original comment by steven.b...@gmail.com on 5 Aug 2012 at 9:04

• Added labels: Type-Task
• Removed labels: Type-Defect

[GoogleCodeExporter]

The 1.2 release is covered, so I'm moving this to 1.3.

Original comment by steven.b...@gmail.com on 16 Aug 2012 at 1:05

• Added labels: Milestone-1.3
• Removed labels: Milestone-1.2

[GoogleCodeExporter]

Original comment by lee.becker on 17 Feb 2013 at 6:01

• Added labels: Milestone-1.4
• Removed labels: Milestone-1.3

[GoogleCodeExporter]

We're now marking Milestones on all our issues, and providing links like:

https://code.google.com/p/cleartk/issues/list?can=1&q=Milestone%3D1.4+-is%3Aopen

And we've decided that it's not a good use of time to go back and try to figure 
out all the 1.1 issues. So I'm closing this issue.

Original comment by steven.b...@gmail.com on 28 Mar 2013 at 4:09

• Changed state: Fixed