Hi Dan, Sounds good. In which case, I'll stick to my original plan, i.e., to submit the package for BioC 3.4. We can figure out what to do with the workflow and build system then, if it hasn't already been sorted.
Cheers, Aaron Dan Tenenbaum wrote: > Hi, > > This has come up before and probably should be done at some point. > I can be virtually certain that it will not happen before the upcoming (3.3) > release though. > > Thanks. > Dan > > > ----- Original Message ----- >> From: "Michael Love" <michaelisaiahl...@gmail.com> >> To: "Aaron Lun" <a...@wehi.edu.au> >> Cc: "bioc-devel" <bioc-devel@r-project.org> >> Sent: Sunday, February 28, 2016 5:59:41 AM >> Subject: Re: [Bioc-devel] workflows running Bioc-devel >> +1 >> >> I'm also interested in having the option of devel / release workflow >> branches for the reasons Aaron mentions. >> >> I develop software and workflow in tandem but currently there is a >> disconnect in showing publicly how software changes will impact a workflow. >> >> [[alternative HTML version deleted]] >> >> _______________________________________________ >> 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
