Hello Again,
I would be happy to submit the github master with the patch tonight if you
could please confirm the commit command. Will it be tested before
integration I assume.
Thanks a lot!
Best wishes.
*Stefano *
Stefano Mangiola | Postdoctoral fellow
Papenfuss Laboratory
The Walter Eliza Hall Institute of Medical Research
+61 (0)466452544
Il giorno mer 3 giu 2020 alle ore 12:26 stefano <mangiolastefano at gmail.com>
ha scritto:
Thanks Lori, (it seems outlook lost my sent email)
sorry I missed this. It's so strange, few days ago I checked at
https://www.bioconductor.org/packages/devel/bioc/html/tidybulk.html
and the build was OK for devel and stable versions.
I have done the fix
commit d1fe5beb290765181e0ce377b890f453c62ea9da
Should I (?)
- integrate the commit to the tidybulk version present in Bioconductor,
and push
- or push the update github repo
Could you point me to the resource tat states how to push to Bioconductor,
so I'm sure I am doing the right thing.
Thanks alot.
Best wishes.
*Stefano *
Stefano Mangiola | Postdoctoral fellow
Papenfuss Laboratory
The Walter Eliza Hall Institute of Medical Research
+61 (0)466452544
Il giorno mer 3 giu 2020 alle ore 07:10 Shepherd, Lori <
Lori.Shepherd at roswellpark.org> ha scritto:
Hello Package Maintainer,
The Bioconductor Team would like to notify you that your package is
currently
failing on release and devel versions of Bioconductor and has been for an
extended period of time. This is very problematic. Please fix your
package to
R CMD build and R CMD check cleanly immediately to avoid deprecation of
your
package. If you are having trouble or have any further questions please
reach
out to the developers mailing list at bioc-devel at r-project.org
We appreciate your immediate attention to this matter.
Cheers
http://bioconductor.org/checkResults/devel/bioc-LATEST/tidybulkhttp://bioconductor.org/checkResults/release/bioc-LATEST/tidybulk
Lori Shepherd
Bioconductor Core Team
Roswell Park Comprehensive Cancer Center
Department of Biostatistics & Bioinformatics
Elm & Carlton Streets
Buffalo, New York 14263
This email message may contain legally privileged and/or confidential
information. If you are not the intended recipient(s), or the employee or
agent responsible for the delivery of this message to the intended
recipient(s), you are hereby notified that any disclosure, copying,
distribution, or use of this email message is prohibited. If you have
received this message in error, please notify the sender immediately by
e-mail and delete this email message from your computer. Thank you.
From: stefano <mangiolastefano at gmail.com>
Sent: Wednesday, June 3, 2020 4:29 AM
To: Shepherd, Lori <Lori.Shepherd at RoswellPark.org>; bioc-devel at r-project.org <bioc-devel at r-project.org>
Subject: Re: Bioconductor package tidybulk
Thanks Lori,
I have to questions
1)
I got versioning error
```
rstudio-1 267 % git push upstream master
Counting objects: 372, done.
Delta compression using up to 32 threads.
Compressing objects: 100% (276/276), done.
Writing objects: 100% (290/290), 1.13 MiB | 0 bytes/s, done.
Total 290 (delta 208), reused 21 (delta 13)
remote: Resolving deltas: 100% (208/208), completed with 41 local objects.
*remote: Error: Illegal version bump from '1.1.0' to '1.2.1'. Check *
remote: http://bioconductor.org/developers/how-to/version-numbering/
remote: for details
To git at git.bioconductor.org:packages/tidybulk.git
```
Even reading the guide
http://bioconductor.org/developers/how-to/version-numbering/ I don't
understand what applies to my case
2) I still don't know what is the best way to manage github development
with Bioconductor development.
I have my Master branch and I am pushing it to Bioconductor. Can I have a
RELEASE branch pushed to Bioconductor rather than my master branch?
guide: "Repeat for the release branch, replacing master with the name of
the release branch, e.g., RELEASE_3_6."
Thanks.
Best wishes.
*Stefano *
Stefano Mangiola | Postdoctoral fellow
Papenfuss Laboratory
The Walter Eliza Hall Institute of Medical Research
+61 (0)466452544
Il giorno mer 3 giu 2020 alle ore 23:36 Shepherd, Lori <
Lori.Shepherd at roswellpark.org> ha scritto:
The master branch is the development branch (Bioc 3.12) . The version of x.y.z The y is always odd in devel and even in release. This is the very first section on the page you referenced. http://bioconductor.org/developers/how-to/version-numbering/
We do not jump full y versions in the middle of a release.
The current RELEASE_3_11 version is 1.0.0 = the appropriate version bump on this branch is 1.0.1
The current master version is 1.1.0 = the appropriate version bump on this branch is 1.1.1
If you are unfamiliar with git and github branches I encourage you to read more documentation about it. There are many helpful tutorials.
You can have as many branches on your local github repository as you like. We recommend creating unique branches for bioconductor releases to mimic our branch structure. In general, and to make it less confusing we would highly recommend using the master branch as the development branch and link that to the master (development version) of Bioconductor. This would be consistent and then you can following the guides and tutorials listed on the Bioconductor help pages
http://bioconductor.org/developers/how-to/git/
The release branch is designed to always be a stable branch and should only be updated for bug corrections.
The master branch should be for development and new features.
We will assume you ran the following to set up your remotes as recommended:
git remote add upstream git at git.bioconductor.org:packages/tidybulk.git
if you do
git remote -v
you should see something similar:
origin <link to your github> (fetch)
origin <link to your github> (push)
upstream git at git.bioconductor.org:packages/tidybulk.git (fetch)
upstream git at git.bioconductor.org:packages/tidybulk.git (push)
To create and work on a release branch:
git fetch --all
# this gets all branches from all remotes
# The following would only need to be run once EVER!
git checkout -b RELEASE_3_11 upstream/RELEASE_3_11
# this says checkout a branch (-b) call it RELEASE_3_11 and have it copied/link to the code at upstream/RELEASE_3_11 (the #bioconductor upstream remote branch of RELEASE_3_11)
After it is created, to switch to this branch on a daily basis you can simply:
git checkout RELEASE_3_11
git pull upstream RELEASE_3_11
# pulls changes from the upstream RELEASE_3_11 remote
# The following would only need to be run once EVER! It creates a branch on your local github called RELEASE_3_11
git push -u origin RELEASE_3_11
Make your code changes to fix bugs! Make sure to do a valid version bump by bumping the z of version x.y.z
git add <files>
git commit # give an informative commit message
git push upstream RELEASE_3_11
# This should push to the Bioconductor git repository
git push origin RELEASE_3_11
# This should push to your github local git repository
git checkout master
# Switch back to your master branch for development and code changes
If you are ever confused on what branch you are on you can do
git branch
To work on the devel master branch the commands would be similar to above but using master
git pull upstream master # pulls from git bioconductor
git pull origin master # pull from your individual github
# make changes, commit changes
git push upstream master # pushes to git Bioconductor
git push origin master # push to your github
Hopefully that helped clarified and will get you started.
Lori Shepherd
Bioconductor Core Team
Roswell Park Comprehensive Cancer Center
Department of Biostatistics & Bioinformatics
Elm & Carlton Streets
Buffalo, New York 14263
From: stefano <mangiolastefano at gmail.com>
Sent: Thursday, June 4, 2020 12:56 AM
To: Shepherd, Lori <Lori.Shepherd at RoswellPark.org>
Cc: bioc-devel at r-project.org <bioc-devel at r-project.org>
Subject: Re: Bioconductor package tidybulk
Thanks Lori,
your email finally made me understand the relationship between my repo and
Bioc repo. I have to admit that I was not familiar of remote vs. upstream.
Now, I have pushed everything to RELEASE_3_11. But the tests did not
trigger.
I will push to develop as well early next week.
Best wishes.
*Stefano *
Stefano Mangiola | Postdoctoral fellow
Papenfuss Laboratory
The Walter Eliza Hall Institute of Medical Research
+61 (0)466452544
Il giorno gio 4 giu 2020 alle ore 23:11 Shepherd, Lori <
Lori.Shepherd at roswellpark.org> ha scritto:
Thanks Lori,
your email finally made me understand the relationship between my repo and
Bioc repo. I have to admit that I was not familiar of remote vs. upstream.
Now, I have pushed everything to RELEASE_3_11. But the tests did not
trigger.
I will push to develop as well early next week.
Best wishes.
*Stefano *
Stefano Mangiola | Postdoctoral fellow
Papenfuss Laboratory
The Walter Eliza Hall Institute of Medical Research
+61 (0)466452544
Il giorno gio 4 giu 2020 alle ore 23:11 Shepherd, Lori <
Lori.Shepherd at roswellpark.org> ha scritto: