On 8/14/19 10:19, Kasper Daniel Hansen wrote:
...
>
> Pro-tip: In general, you will be well served not to get too attached to
> version numbers. Bump it frequently even without new functionality or bug
> fixes and just live with the frequent bumping.
+1 for Best Advice Of The Week.
--
Hervé
Yes, it will build the most recent version
If the previous build failed it will even build the most recent code, even
if the code is not bumped. The exception is the following
you update package A to version X, build succeeds
you commit code to package A, but does not bump the version
This
Yes, the Bioconductor build system will only try to build the most recent
version in the git repository. If it never managed to successfully build a
particular version then that version should not appear anywhere on the Bioc
site. For example biomaRt is now on release 2.40.3, but version 2.40.2
Thank you for the prompt response! I will just add more versions on top of what
I have already added. Would it be correct to assume that Bioconductor will try
to build the most recent version available, even though it failed builds for
previous versions?
Regarding the change, it was indeed a
Sorry about any confusion I created. The forum is still on as far as I
know.
Sean
On Wed, Aug 14, 2019 at 11:21 AM Leonardo Collado Torres <
lcollado...@gmail.com> wrote:
> Hi everyone,
>
> I think this caused a bit of confusion. My understanding was that Sean
> created a google calendar event
Hi everyone,
I think this caused a bit of confusion. My understanding was that Sean
created a google calendar event and cc'ed the bioc-dev mailing list.
In any case, from what I can see at the BioC slack in the #general
channel, the forum is still scheduled for tomorrow Thursday August
15th.
You cannot revert. By pushing those updates, you released a version into
the wild. It is true that as long as it doesn't build on the build servers,
it would have been hard to obtain for anyone, but it is still possible
through git. You need to update the version.
Best,
Kasper
On Wed, Aug 14,
Also, it is not clear to me if this qualifies for a update to the release
branch. Updates to release should be restricted to critical bug fixes
(although if tidyr updates will break your package, that sounds like a
critical bug fix to me)
Note to others: this (again) emphasizes that we may need
I made some changes to my seqCAT package the last few days in order to prepare
for version 1.0.0 of tidyr, which was apparently harder than I initially
thought. I was also a bit too quick with pushing to Bioconductor (both the
release and devel branches), and now I’ve got several updates and
