On Thu, Mar 15, 2018, at 11:26 AM, Hervé Pagès wrote:
>
> Just to clarify, all software packages are built and checked every
> night, independently of whether their version got bumped or not.
> The version bump only allows the modified package to propagate
> to the public repo and become available
Hi,
Just to clarify, all software packages are built and checked every
night, independently of whether their version got bumped or not.
The version bump only allows the modified package to propagate
to the public repo and become available via biocLite(), possibly
replacing the previous version of
On Sun, Mar 11, 2018, at 4:10 AM, Egon Willighagen wrote:
> But previously I learned that when you push
> something to the repository, you should bump the question, so currently I
> do this for every change I made, leaving a ridiculous number of minor
> release and really short NEWS entries...
I w
Dear James,
I should have mentioned that email... I had seen it. But I mostly read it
as personal experience. However, given that you refer me to that, I will
assume my proposal is acceptable, as it is comparable to Martin's write up.
Thanks,
Egon
On Sun, Mar 11, 2018 at 5:06 PM, James W. MacD
This was recently discussed:
https://stat.ethz.ch/pipermail/bioc-devel/2018-February/012875.html
On Sun, Mar 11, 2018 at 4:10 AM, Egon Willighagen <
egon.willigha...@gmail.com> wrote:
> Hi Nicolas,
>
> after doing a bit of work on the BridgeDbR package this weekend, I was
> wondering exactly the
Hi Nicolas,
after doing a bit of work on the BridgeDbR package this weekend, I was
wondering exactly the same thing. I prefer small patches, so that I can
easily link the change with the commit message and have related changes
together (and fairly, it allows me to see when I actually work on what
On 02/23/2018 02:24 PM, Nicolas Descostes wrote:
Dear Bioconductor community,
When developing further a package, is the best practice to create a branch
and bump the version when a full new feature is merged or to stay on the
master without bumping when committing temporarily? More generally,
Dear Bioconductor community,
When developing further a package, is the best practice to create a branch
and bump the version when a full new feature is merged or to stay on the
master without bumping when committing temporarily? More generally, When do
you usually bump a version?
Thank you.
Nic
