On 8/9/11 4:05 PM, Phil Steitz wrote:
Thanks for the nudge. I'll bite. Of course anyone is welcome to
browse the open JIRA issues with 3.0 as fix version and add comments
:)
I started slugging through JIRA. Made it all the way through the
unclassified list and will finish the first pass
Phil Steitz wrote:
On 8/9/11 4:05 PM, Phil Steitz wrote:
Thanks for the nudge. I'll bite. Of course anyone is welcome to
browse the open JIRA issues with 3.0 as fix version and add comments
:)
I started slugging through JIRA. Made it all the way through the
unclassified list and will
Does anyone have a list of showstopper bugs and features. If we want a 3.0
release soon, then perhaps some kind of a prioritized list would help us in
the community concentrate some of our efforts? I was thinking that the
individuals with commit privileges could put this together since they are
3.0 came out a couple of weeks ago. :) 3.0.1 is on the way now.
Matt
On Tue, Aug 9, 2011 at 4:59 PM, Greg Sterijevski gsterijev...@gmail.com wrote:
Does anyone have a list of showstopper bugs and features. If we want a 3.0
release soon, then perhaps some kind of a prioritized list would help
My bad! This was indeed for math commons...
On Tue, Aug 9, 2011 at 5:02 PM, Matt Benson gudnabr...@gmail.com wrote:
3.0 came out a couple of weeks ago. :) 3.0.1 is on the way now.
Matt
On Tue, Aug 9, 2011 at 4:59 PM, Greg Sterijevski gsterijev...@gmail.com
wrote:
Does anyone have a
Probably more my own mistake than yours. :)
Regards,
Matt
On Tue, Aug 9, 2011 at 5:50 PM, Greg Sterijevski gsterijev...@gmail.com wrote:
My bad! This was indeed for math commons...
On Tue, Aug 9, 2011 at 5:02 PM, Matt Benson gudnabr...@gmail.com wrote:
3.0 came out a couple of weeks ago.
Thanks for the nudge. I'll bite. Of course anyone is welcome to
browse the open JIRA issues with 3.0 as fix version and add comments
:)
Phil
On Tue, Aug 9, 2011 at 2:59 PM, Greg Sterijevski gsterijev...@gmail.com wrote:
Does anyone have a list of showstopper bugs and features. If we want a
Btw (aimed to Greg and anyone else) - never feel that the committers
would be best to put it together. I've gotten Open Source projects out
the door without being a committer simply by listing the things I/they
thought they should work on on a wiki. It's a bit more of a pain
without access to
Yes, criticism well made. However, in solving the voting problem, the fewer
the voters and the fewer the choices, the quicker that a solution can be
determined. The worry is that 1000 people pull in 1000 directions, as
opposed to 10 people pulling in 6 directions. ;-)
On Tue, Aug 9, 2011 at
Heh - s/criticism/encouragement :)
On Tue, Aug 9, 2011 at 5:45 PM, Greg Sterijevski gsterijev...@gmail.com wrote:
Yes, criticism well made. However, in solving the voting problem, the fewer
the voters and the fewer the choices, the quicker that a solution can be
determined. The worry is that
Hey guys, I guess we should have a thorough look at this process
for our own 3.0 release.
We are clearly late and we have a huge pile of unsorted issues. Many
people open more and more requests while we try to solve them, as can be
seen from Jira activity in the last few months.
People start
Hello.
Hey guys, I guess we should have a thorough look at this process
for our own 3.0 release.
We are clearly late and we have a huge pile of unsorted issues. Many
people open more and more requests while we try to solve them, as
can be seen from Jira activity in the last few months.
If you are trying to get a 3.0 release out ASAP, you just need to
address showstopper bugs.
If a new package is too new and shiny to put out and not fully baked,
consider taking it out of 3.0. Radical but simple.
The exceptions issue is tricky you want to have something stable for
future
On 7/29/11 12:11 AM, Luc Maisonobe wrote:
Hey guys, I guess we should have a thorough look at this process
for our own 3.0 release.
We are clearly late and we have a huge pile of unsorted issues.
Many people open more and more requests while we try to solve
them, as can be seen from Jira
14 matches
Mail list logo
