William Stein wrote:
On Mon, Mar 8, 2010 at 8:25 PM, Nick Alexander wrote:
Okay, then you tell people that their hard work will not be packaged in the
next iteration. Maybe that's life, but it will certainly discourage me from
contributing when I'm told in advance that my changes will not be
Hi William,
The information in this thread goes straight to the FAQ.
--
Regards
Minh Van Nguyen
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
sage-devel+unsubscr...@googlegroups.com
For more options, visit this group at
On Mon, Mar 8, 2010 at 8:25 PM, Nick Alexander wrote:
In my personal opinion, a decent stabilisation release could be achieved
by everyone submitting just bug fixes.
>>>
>>> Yep. The problem is that this involves telling everyone what to do.
>>
>> Not really. You tell people what a relea
In my personal opinion, a decent stabilisation release could be
achieved by everyone submitting just bug fixes.
Yep. The problem is that this involves telling everyone what to do.
Not really. You tell people what a release will consist of. It is to
them whether or not they want to submit bug
Robert Bradshaw wrote:
On Mar 7, 2010, at 5:07 AM, Dr. David Kirkby wrote:
Robert Bradshaw wrote:
On Mar 6, 2010, at 4:50 PM, Dr. David Kirkby wrote:
I thought there was going to be a 4.4 stabilisation release, but if
I create a new trac ticket, I'm given the milestone options are
4.3.4 and
On Mar 7, 2010, at 5:07 AM, Dr. David Kirkby wrote:
Robert Bradshaw wrote:
On Mar 6, 2010, at 4:50 PM, Dr. David Kirkby wrote:
I thought there was going to be a 4.4 stabilisation release, but
if I create a new trac ticket, I'm given the milestone options are
4.3.4 and 4.5 - there is no 4.4
Dr. David Kirkby wrote:
Having a rule that
* Now updates to standard packages (since these often introduce as many
problems as they solve)
* Only bug fixes - no enhancements.
then IMHO, we could stabilise Sage somewhat.
Sorry, I was suggesting there were *no* updates to standard packages
Robert Bradshaw wrote:
On Mar 6, 2010, at 4:50 PM, Dr. David Kirkby wrote:
I thought there was going to be a 4.4 stabilisation release, but if I
create a new trac ticket, I'm given the milestone options are 4.3.4
and 4.5 - there is no 4.4 choice.
IMHO, it would be good if the stabilisation r
On Mar 6, 2010, at 4:50 PM, Dr. David Kirkby wrote:
I thought there was going to be a 4.4 stabilisation release, but if
I create a new trac ticket, I'm given the milestone options are
4.3.4 and 4.5 - there is no 4.4 choice.
IMHO, it would be good if the stabilisation release did go ahead,
I thought there was going to be a 4.4 stabilisation release, but if I create a
new trac ticket, I'm given the milestone options are 4.3.4 and 4.5 - there is no
4.4 choice.
IMHO, it would be good if the stabilisation release did go ahead, and *only*
bug-fixes were permitted. i.e. no new code to
10 matches
Mail list logo