[Bioc-devel] ICE accepted

Herve Pages hpages at fhcrc.org
Wed Aug 29 18:48:44 CEST 2007 

Rob Scharpf wrote:
> Hi Herv,
> 
> I didn't realize there was a package named 'ICE' in the cran
> repository.  Should we change the name?

Absolutely! It's good that you catched this before the release! Tell me what
name you want and I'll rename the top folder in subversion. Then I'll let you
make all the required changes in the package itself, starting with the
DESCRIPTION file.
When this is done, I'll send a short notice to the reviewers so they are
not to surprised to see your package showing up on the public repo under
a different name.

Thanks!

H.

PS: I've added a note to our package guidelines about this
  http://wiki.fhcrc.org/bioc/Package_Guidelines#package-name

> 
> R
> 
> 
> On Aug 27, 2007, at 8:09 PM, Herve Pages wrote:
> 
>> Hi Rob,
>>
>> This is the follow up on Issue18 in our Issue tracker. Let's keep this
>> out of
>> the tracker and use regular email from now.
>>
>> I've added the source of the ICE package to our Subversion repository
>> and to our automated builds for Bioconductor 2.1 (current devel). It
>> should
>> show up on this page
>>
>>   http://bioconductor.org/checkResults/2.1/bioc-LATEST/
>>
>> tomorrow around midnight (Seattle time). Let me know if it doesn't.
>> The above report is updated every day with the last build/check results
>> obtained on the different platforms that we use for testing BioC devel.
>>
>> A devel package is made publicly available (by being pushed to
>> http://bioconductor.org/packages/2.1/bioc/) only if it passes the CHECK
>> test on lamb1 with no error (it can have warnings though). Then
>> the easiest way to install it is to use biocLite() (from R-devel):
>>
>>> source("http://bioconductor.org/biocLite.R")
>>> biocLite("package_name")
>>
>> I didn't need to request a Subversion account for you since you
>> already have
>> one. However I've include at the end of this email the standard
>> information
>> I send to every new Bioconductor official maintainer, just in case.
>>
>> For more general questions or advice about the development/maintenance of
>> your package, please use the Bioc-devel mailing list (our primary channel
>> for communication between developers and for important announcements like
>> release schedules, build system news, etc...).
>>
>> Finally it's probably a good time for us to remind you that, as a
>> Bioconductor
>> maintainer, it is your responsability to:
>>
>>   1. Subscribe to the bioc-devel mailing list (if you have not done it
>> yet).
>>
>>   2. Respond to bug reports and questions from users regarding your
>> package.
>>
>>   3. Maintain your package and its capabilities as R and other
>> Bioconductor
>>      packages evolve. Typically this involves some work every six months,
>>      when a new release is being prepared. We can assist by answering
>>      questions, but it is your responsibility to look for and make any
>> needed
>>      changes. If you are unwilling or unable to do this your package
>> will be
>>      removed from the upcoming release. Users will still be able to
>> find the
>>      older versions.
>>
>> Best regards, and thank you for contributing to the Bioconductor project!
>>
>> H.
>>
>>
>> ==============================================================================
>>
>>
>> Subversion Quick Start
>> ----------------------
>>
>> You will need the Subversion client (the 'svn' command) in order to
>> access our Subversion repository.  Typical use:
>>
>>   o Check out your package with:
>>       svn co
>> https://hedgehog.fhcrc.org/bioconductor/trunk/madman/Rpacks/your_package/
>>     This will create a working copy of the package source tree on
>>     your local disk.  You can edit the files, add new files (first
>>     create the new file, then put it under revision control with
>>     'svn add <newfile>'), delete files (with 'svn del <file>')
>>     and rename files (with 'svn rename <file>').
>>
>>   o Once you are done, commit your changes with:
>>       cd top/directory/of/your/package
>>       svn ci -m 'comment your changes here'
>>
>>   o Next time you want to work again on the package, don't forget
>>     to 'svn update' first (no need to check out the whole source
>>     tree again):
>>       cd top/directory/of/your/package
>>       svn up
>>
>> You have global read access to the Bioconductor repository and
>> read/write access to your own package directory.
>>
>>
>> More about Subversion
>> ---------------------
>>
>> - The Subversion command line client is available here:
>>     http://subversion.tigris.org/project_packages.html
>>
>> - Windows users looking for a GUI interface should look at the
>>   TortoiseSVN project (http://tortoisesvn.tigris.org).
>>
>> - If you plan to build the Subversion client from source, be sure to
>>   include support for HTTPS by adding "--with-ssl" to the configure
>>   line.
>>
>> - Read _our_ SVN How To page at
>>     http://wiki.fhcrc.org/bioc/SvnHowTo
>>
>>
>> How we build, test and publish the Bioconductor packages
>> --------------------------------------------------------
>>
>> Please, keep an eye on the build/check result page for the
>> Bioconductor devel packages (currently BioC 2.1):
>>
>>   http://bioconductor.org/checkResults/2.1/bioc-LATEST/
>>
>> A devel package is made publicly available (by being pushed to
>> http://bioconductor.org/packages/2.1/bioc/) only if it passes the CHECK
>> test on lamb1 with no error (it can have warnings though). Then the
>> easiest (and recommended) way to install it is to use biocLite() (from
>> R-devel):
>>
>>> source("http://bioconductor.org/biocLite.R")
>>> biocLite("package_name")
>>
>> However, if your package is already published and you make changes
>> to it, the new version will not replace the old version unless
>> you have bumped z in the version number x.y.z. DON'T FORGET TO
>> BUMP Z! or the last version of your package will not be pushed
>> to http://bioconductor.org/packages/2.1/bioc/
>>
>>
>> Mailing lists
>> -------------
>>
>> Let me know or ask on the Bioc-devel mailing list
>> (bioc-devel at stat.math.ethz.ch) if you have any question.
>> Also, when your package will pass the CHECK test for the first time,
>> we strongly encourage you to send a note to Bioc-devel to announce
>> its public avaibility (with a short description) so other people
>> can start to test it.
>>
>> Finally, if you have not already done so, we urge you to
>> subscribe to the Bioconductor mailing list so that you can
>> answer questions from users of your package and respond to bug
>> reports promptly. You can find the information about the mailing
>> lists here:
>>
>>   http://bioconductor.org/docs/mailList.html
>>
>>
>> Thanks for contributing to the Bioconductor project!

More information about the Bioc-devel mailing list