On Nov 29, 7:37 pm, Minh Nguyen <[EMAIL PROTECTED]> wrote:
> Hi Michael,
Hi Minh,
> mabshoff wrote:
>
> [...]
>
> >> If this sounds a bit abstract, have a look at ticket #4534, which is a
> >> concrete example similar to what I've described above:
>
> >>http://trac.sagemath.org/sage_trac/ticket/4534
>
> > That ticket has two independent patches, one each reviewed by two
> > different people even though RobertWB's comment never was formally a
> > review, just a comment. Only the second patch was merged in that
> > particular case and only Jaap got formal reviewer credit in that case.
>
> OK, this an answer I've been waiting for. So you're saying that the
> reviewer(s) of a merged patch get credit. Is that it?
Yep, that is it in 99.5% of the cases. There are some tickets that are
messier, but those are usually a gut call.
> > To get back to release notes in general: Are you planning to write
> > that part of the release notes since I record that info (and other
> > info, too) while merging patches.
>
> OK, since you're handling this as a milestone progresses, then I don't
> want to duplicate effort here.
Ok, good to know. It can't hurt to check the credits, but I don't
think this is something we have had significant problems with in the
past. I do recall maybe two or three emails about the credits in the
release notes since we do list the credit for reviews.
> > The individual changes for alphas
> > and rcs are usually pasted after the release notes, so if you wanted
> > to verify what has been noted I would greatly prefer it to get an
> > email on list pointing out potential issues. Once we get closer to a
> > final release someone needs to proof read my draft and potentially add
> > a bunch of additional boilerplate to what I have written.
>
> I assume that such a draft for each milestone is uploaded to trac, the
> draft is attached to a ticket, and that ticket is assigned to the said
> milestone. If that's the case, then I'd be more than happy to check your
> draft and add some high-level stuff if need be. But my little bit of
> concern is, how do I know when you've created such a ticket with a draft
> of your release note? For example, would the notification be via email
> to sage-devel, or some other means of notification?
Usually the final release notes are written once the sage-x.y.z
tarball has been released since we only announce once binaries have
been build and uploaded. That usually gives you and me a 24 to 48 hour
windows before the announcement goes out. It might be better if the
final tarball would already contain the latest release notes, but that
does cut it pretty close. In the end most things can be checked and
the boilerplate can be filled in once we get close to the final
planned rc, but we would have to see how that works out.
> > Another
> > thing that would be nice if you could handle it is the Sage Release
> > tour in the wiki since that can easily be done while the release is
> > progressing and since it is in the wiki it is trivial to do with
> > multiple parties at the same time.
>
> Yes, I think I can do that, with some bugging of folks on sage-devel
> when I seem to be confused about particular tickets.
Yep, feel free to bother people since that works well :)
> > One last thing: Can you take a look and review the various draft2 text
> > files #4567? In case you do please post a diff with your changes - I
> > really want to send the official notices out, but have been waiting
> > for you.
>
> Sorry about my lateness in replying to this issue. (I have a full-time
> job this 2008/2009 Australian summer :-)
Most of us have to work for a living, so don't worry about it. I was
just curious since you seemed to have dropped from the net for a
couple days after being enthusiastic.
> I'm doing some basic checking
> right now. I'll upload a diff to #4567 within one hour from this post.
Thanks. I believe the greatest impact will be if the Release Tour is
nice and polished. The HISTORY.txt cleanup project is also something
worth doing and that one has the advantage that it is not time
critical.
In general if anybody else wants to help out that person would be more
than welcome since there is more than enough work to go around for
everybody. So don't hesitate to pipe up, even if you have only little
free time to contribute. Every bit is deeply appreciated and in the
end it is great fun :)
> --
> Regards,
> Minh Van Nguyen
Cheers,
Michael
>
> Web:http://nguyenminh2.googlepages.com
> Blog:http://mvngu.wordpress.com
--~--~---------~--~----~------------~-------~--~----~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~----------~----~----~----~------~----~------~--~---
