Dear all,
I am working on creating several vignettes for my recently released package
(artMS), instead of having only a long one (as suggested by the bioc
reviewer). Two questions:
- Is there a way to link vignettes between themselves? For example, if I
have 3 new vignettes, let’s say
Hi Kylie,
I've modified coerce2() in S4Vectors 0.21.5 so that `coerce2(from, to)` should
now do the right thing when 'to' is a DataFrame derivative:
https://github.com/Bioconductor/S4Vectors/commit/48e11dd2c8d474c63e09a69ee7d2d2ec35d7307a
With the following gotcha: this will work only if
Dear all,
Are there any plans to export coerce2() from the S4Vectors namespace, like
other exported internal utilities such as showAsCell() and setListElement()?
I have a couple classes that inherit from DataFrame, and some inherited methods
(like [[<-) break in certain situations due to calls
I'm going to try to provide some details, at the risk to confuse you even more.
In BioC 3.8 / R 3.5 base::lengths() was not just slow on some Bioconductor
objects like IRanges or GRanges, it didn't work:
> ir <- IRanges(1:21, 20)
> base::lengths(ir)
Error in getListElement(x, i, ...) :
Thank you Martin and Shepherd, now I am much more familiar with this version
control pipeline. I will focus on the master branch (devel) in the future.
Best wishes,
Wenhao
发件人: Martin Morgan
发送时间: 2018年11月13日 20:05:54
收件人: Tang, Wenhao;
The middle version on the master branch needs to be odd, so 1.1.3; trying to
push 1.0.5 to the master branch of the git.bioconductor.org remote will not
work.
The correct way to manage this is to separately bump versions on the
RELEASE_3_8 branch and on the master branch, and to separately
Version numbering in devel and release will ALWAYS be different as described
http://bioconductor.org/developers/how-to/version-numbering/
In a package version package_x.y.z -
Y in devel will always be odd and 1 greater than that in release
Y in release will always be even and 1 less than
Dear all,
Now I understand how to sync my local master, local RELEASE_3_8, remote master
and remote RELEASE_3_8.
All of them have version 1.0.5. I also want to update the DEVEL branch, but
when I did (the step 9 in
http://bioconductor.org/developers/how-to/git/sync-existing-repositories/)
To summarize some further discussions we had on this, with the bottom
line that it needs more thought:
The proposal amounts to establishing a third generation of media used
for academic publishing:
1. Printed paper (since 1665)
2. Portable document format (PDF) files (since 1990s)
3.
