On Monday, May 5, 2014 10:10:27 AM UTC-4, Ralf Stephan wrote:
>
>
> 3. why not show the sage version the ticket was based and tested on
> by patchbot on the trac blob? What reason is there to show "6.1.1"
> when the ticket was tested by patchbots both a) by merging a develop
> version into 6.1.1 (so it's develop anyway) and b) based on current
> develop.
>
The functionality to create the blobs you want is already there, e.g.
http://patchbot.sagemath.org/ticket/11719/status.png?base=6.2.rc2
I agree it would be nice to display the latest non-trivial blob by default.
To do this, you could improve the function which makes the blob so that,
when no base is given, it checks to see which is the latest base the ticket
was tested on and returns the corresponding blob. I believe that function
is create_status_image:
https://github.com/robertwb/sage-patchbot/blob/3482b9d7f7fa76dbdb8553b3a3eab5acf2aedb9f/src/serve.py#L462
To support this, and maybe other patchbot interfacing, it would help to
have a function which returns the most recent base on which the ticket was
tested. I'm not quite sure what "recent bases" should be checked -- maybe
the list of tagged commits ordered by containment? Maybe going back only
to the most recent official release?
-Niles
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.
