Spring Cleaning

8 views
Skip to first unread message

Omer Katz

unread,
Jul 19, 2013, 5:54:59 AM7/19/13
to nose...@googlegroups.com
I know it's summer but I have taken the liberty to perform some issues cleanup.
I added new labels, responded to old issues and added a milestone for 0.5.0 & 1.0.0.

I marked issues where a decision is needed in order to proceed handling them.
I also marked issues where more information is needed in order to proceed handling them.

There are currently only two release blockers which should be handled as soon as possible in order to be able to work on 0.5.0.

I believe that we should integration our CI with coveralls.io so we can keep track of our own code coverage. See issue #108 for details.

I suggest to declare 0.5.x as a maintenance release with only minor new features.
That means solving all trivial & non-trivial bugs that were not assigned to the 1.0.0 release, making sure code coverage is high and writing more tests in order to discover more bugs.

jason pellerin

unread,
Jul 19, 2013, 10:17:13 AM7/19/13
to nose...@googlegroups.com
Thank you very very much for this. It is a huge help. I agree with the release plan for 0.5.0.



--
You received this message because you are subscribed to the Google Groups "nose-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to nose-dev+u...@googlegroups.com.
To post to this group, send email to nose...@googlegroups.com.
Visit this group at http://groups.google.com/group/nose-dev.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

Reply all
Reply to author
Forward
0 new messages