In Addition to Nitesh's comments: Please do not push the version to 1.0.0 yourself. This will be done at the time of release by the core team. Continue to increment z of verion x.y.z. For example 0.99.5.
For now, you have to wait for a nightly build to view the results of the build/check. http://bioconductor.org/checkResults/devel/bioc-LATEST/TimiRGeN/ Information on timing of build report and how long from push to viewing is summarized at the top of this page: http://bioconductor.org/developers/how-to/troubleshoot-build-report/ Remember new builds will only register with a valid version bump. You could always create a temporary directory and try checking the code out from git.bioconductor.org to see if the changes got successfully pushed to the server. Or check out the RSS feed Cheers, Lori Shepherd Bioconductor Core Team Roswell Park Comprehensive Cancer Center Department of Biostatistics & Bioinformatics Elm & Carlton Streets Buffalo, New York 14263 ________________________________ From: Bioc-devel <bioc-devel-boun...@r-project.org> on behalf of Krutik Patel (PGR) <k.pat...@newcastle.ac.uk> Sent: Friday, September 18, 2020 5:01 AM To: bioc-devel@r-project.org <bioc-devel@r-project.org> Subject: [Bioc-devel] Few questions of maintaining a new bioconductor package Dear Bioconductor team, I've recently had my package, TimiRGeN, accepted into bioconductor and have a few questions on the maintenance side of things. 1) I am ready to push a newer version of the package. Will I have to set the version to 1.0.0 now? Currently it is version 0.99.4158. 2) Once pushed, how can I check if the build has been successful? Will I have to wait and see if it has passed the nightly builds on build/checkResults? Or is there a faster method. 3) I would like to set up a new SSH key and use this to maintain my package. To do this I will need to activate my account on Bioconductor Git Credentials, but I do not remember setting up a password for this. Any help in these matters would be great. Best, Krutik [[alternative HTML version deleted]] _______________________________________________ Bioc-devel@r-project.org mailing list https://secure-web.cisco.com/1N9JTq9dmE62aCcK0jY2e9hma_u-zPCjcGL_mljxPLb0eDq7zD_2o_qjLUe1liO0r-RSxQlkQ8svE9VrU1TW03csGPOz06yAtgFBRBu2xsXKZJC1ZQxlVK5MLbzEp6BJ_QC6fzzuoPS_jr6Pd03IroGsRwAHWIBZjmkPR3HwAFETaIyKyjJ-s2WlDot3-nqLqYVDE6UMzKg8CiaSgovdQsVaeWsPisTtRpa21w1oMdz_51AVw4nMjnRB0z8LH_SfJxP9HBKccpDVLBSVc2A8h4HzwwwvEMY94vtuzw-sAnlP_XL8_wiEoXAaZGevK0VKb/https%3A%2F%2Fstat.ethz.ch%2Fmailman%2Flistinfo%2Fbioc-devel 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. [[alternative HTML version deleted]] _______________________________________________ Bioc-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/bioc-devel
