On Wed, Jun 3, 2009 at 1:32 AM, Robert Bradshaw
<rober...@math.washington.edu> wrote:
>
> On Jun 2, 2009, at 8:23 AM, Harald Schilly wrote:
>
>> On Jun 2, 9:12 am, William Stein <wst...@gmail.com> wrote:
>>>
>>> Should we start a "sage-release" mailing list for planning releases
>>> and discussing build issues?
>>
>> Personally, I like it if it sticks here on sage-devel. We could tag
>> each subject by a scheme, like in trac, so that we know it is about
>> release management. e.g. "[release x.y.z]". And if there are build
>> issues, it probably falls back to sage-devel by a cross post
>> anyways...
>
> I would see build issues being part of the release list as well, I
> think most people don't need to see (built fine on my machine, here's
> the list of test failures...) but such information is invaluably
> useful to the release manager. Personally, I'd also rather (mentally)
> filter by [sage-release] than [sage-devel] [release x.y.z], but
> that's a minor point. The announcements of alphas/betas/release
> candidates could still go to sage-devel, but the subsequent
> discussion would not.
>
> Another thing I'd like to see is the use of a wishlist and/or roadmap
> wiki page. This would list biggish items, like the switch to new
> symbolics, more robust notebook, new categories system, interactive
> plots, etc. that are bigger in scope than single tickets and whose
> completion merit a full x.y release. (x.y.z releases could continue
> to be the set all positively reviewed tickets + bug fixes as they are
> now.) Basically, in some ways it'd be like a wishlist, but for things
> that need more discussion and planning than a wishlist trac ticket
> ticket/feature request. I think this would also give us a more
> visible direction and focus for the future of Sage as well. As Sage
> is still essentially a volunteer-driven effort, no milestones would
> be attached to them until someone actually stepped up and implemented
> them and they're ready to go in. Other goals, such as doctest and
> documentation coverage, could go there as well. Thoughts?
>
I created sage-release. What's the worst that could happen?
http://groups.google.com/group/sage-release
Please join if you're interested in helping with Sage release
management and the Sage release process in general!
William
--~--~---------~--~----~------------~-------~--~----~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to
sage-devel-unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~----------~----~----~----~------~----~------~--~---
