On 9/30/09 23:54, Derek Baum wrote:
I've assigned all fixed and closed gogo issues to release 0.2.0, which
I have now marked as released (on 15th September).
I've only assigned one of the 10 open issues to the next release,
0.4.0, as I believe that most of the others require some discussion or
confirmation before they are implemented.
If you do assign it to a release and then change your mind, you can
always move it back off.
For me, I often find it easier to assign things to the next release even
if I am not sure about them, because then in JIRA's open issue view, I
can easily click on the version and see the issues being considered. If
they don't make it for this release, I move them off to the next before
doing the release.
But, that is entirely up to you.
-> richard
Derek
2009/9/30 Richard S. Hall<he...@ungoverned.org>:
On 9/30/09 23:25, Derek Baum wrote:
I'm happy to make a start at this.
I see the next version of gogo, 0.4.0 is already defined in Jira.
Yep, so issues targeted for that release should be assigned to it. Not a big
deal, but it gives us a more valuable database...
-> richard
Derek
2009/9/30 Richard S. Hall<he...@ungoverned.org>:
The 0.2.0 version of was released, if I recall correctly. We probably
should
have added a news item on the front page. Also, the 0.2.0 version in JIRA
has not been released. I can take care of, unless there is some reason
not
to.
We should probably start assigning Gogo JIRA issues to JIRA versions to
maintain proper change logs...I don't think any issues have been assigned
versions.
Thanks.
-> richard
