Re: [Bioc-devel] request for more notices about build issues

2015-04-14 Thread Dan Tenenbaum


- Original Message -
 From: Michael Love michaelisaiahl...@gmail.com
 To: bioc-devel@r-project.org
 Sent: Wednesday, April 8, 2015 11:03:02 AM
 Subject: [Bioc-devel] request for more notices about build issues
 
 dear core Bioc-ers,
 
 It would be nice to have more devel mailing list notices about large
 scale build issues, just to keep developers in the loop. (e.g. I
 often
 get a number of emails when GenomicRanges is down, asking why I'm
 breaking someone's downstream package).
 
 Or if you don't want to push these out to the list, to have a URL
 where core team could post information about what's going on in devel
 and rough timelines about upcoming changes. Then developers can
 pull
 this information when they need to.
 
 thanks for all your work! There are lots of exciting things in the
 next release, and I know that's it's a lot of work to get to the
 finish.
 

If it's ok with everyone, I'll address this by just sending email to bioc-devel 
when there are
large-scale build issues. If you see an issue and I don't address it, please 
email the list.

Dan


 best,
 
 Mike
 
 ___
 Bioc-devel@r-project.org mailing list
 https://stat.ethz.ch/mailman/listinfo/bioc-devel


___
Bioc-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/bioc-devel


Re: [Bioc-devel] request for more notices about build issues

2015-04-14 Thread Michael Love
works for me. Thanks Dan.

On Tue, Apr 14, 2015 at 2:34 PM, Dan Tenenbaum dtene...@fredhutch.org wrote:


 - Original Message -
 From: Michael Love michaelisaiahl...@gmail.com
 To: bioc-devel@r-project.org
 Sent: Wednesday, April 8, 2015 11:03:02 AM
 Subject: [Bioc-devel] request for more notices about build issues

 dear core Bioc-ers,

 It would be nice to have more devel mailing list notices about large
 scale build issues, just to keep developers in the loop. (e.g. I
 often
 get a number of emails when GenomicRanges is down, asking why I'm
 breaking someone's downstream package).

 Or if you don't want to push these out to the list, to have a URL
 where core team could post information about what's going on in devel
 and rough timelines about upcoming changes. Then developers can
 pull
 this information when they need to.

 thanks for all your work! There are lots of exciting things in the
 next release, and I know that's it's a lot of work to get to the
 finish.


 If it's ok with everyone, I'll address this by just sending email to 
 bioc-devel when there are
 large-scale build issues. If you see an issue and I don't address it, please 
 email the list.

 Dan


 best,

 Mike

 ___
 Bioc-devel@r-project.org mailing list
 https://stat.ethz.ch/mailman/listinfo/bioc-devel


___
Bioc-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/bioc-devel


Re: [Bioc-devel] request for more notices about build issues

2015-04-08 Thread Sean Davis
Is this a use case for a graphical build report that displays the build
status on a graph/DAG?

http://www.bioconductor.org/packages/release/bioc/vignettes/pkgDepTools/inst/doc/pkgDepTools.pdf

pkgDepTools, combined with a computable build report (a downloadable
version of the current build report), might allow a graphical (in both node
and edge as well as visual) build report.  I could envision a color scheme
applied to a figure like the last figure in the PDF above.  A little
functionality could be built to find the root of a build problem for any
specific package (to the extent that pkgDepTools can capture the
dependencies).

This is not a well-thought-out answer, so take it with a grain of salt.

Sean


On Wed, Apr 8, 2015 at 2:03 PM, Michael Love michaelisaiahl...@gmail.com
wrote:

 dear core Bioc-ers,

 It would be nice to have more devel mailing list notices about large
 scale build issues, just to keep developers in the loop. (e.g. I often
 get a number of emails when GenomicRanges is down, asking why I'm
 breaking someone's downstream package).

 Or if you don't want to push these out to the list, to have a URL
 where core team could post information about what's going on in devel
 and rough timelines about upcoming changes. Then developers can pull
 this information when they need to.

 thanks for all your work! There are lots of exciting things in the
 next release, and I know that's it's a lot of work to get to the
 finish.

 best,

 Mike

 ___
 Bioc-devel@r-project.org mailing list
 https://stat.ethz.ch/mailman/listinfo/bioc-devel


[[alternative HTML version deleted]]

___
Bioc-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/bioc-devel