[Bioc-devel] Confusion with how to maintain release/devel files on local computer.

[Martin Morgan]

On 11/01/2017 04:42 PM, Gabe Becker wrote:
> Arman,
> 
> Not on the Bioc team per se, but I would say only have a checkout of the
> release branch when you need it, ie a bug is reported, you have fixed it in
> devel, and you are ready to push the very narrow bugfix to release. I only
> keep "master" checkouts of my packages on a permanent basis.

In case Arman is not aware, the basic scenarios are at

   https://bioconductor.org/developers/how-to/git

the most straight-forward of which (a clone of the Bioconductor git 
repository, no GitHub mirror) is

   https://bioconductor.org/developers/how-to/git/maintain-bioc-only/

Generally, one has only a single local git repository, switching between 
branches within that repository.

Martin

> 
> You generally shouldn't need a checkout of release, imho, because no
> development should be happening there with exception of the case above.
> 
> Hope that helps,
> ~G
> 
> On Wed, Nov 1, 2017 at 1:36 PM, Arman Shahrisa <shahrisa.arman at hotmail.com>
> wrote:
> 
>> I’m confused with development process.
>>
>> At first, I need to have a folder with accepted packaged. Then I need to
>> pull
>> origion RELEASE_3_6?
>>
>> Then in another folder, I need to pull origion master?
>>
>> So that by opening each folder, I know what I’m editing.
>> Also during push, I need to be careful about where I’m pushing changes.
>> Origion is bioc’s git address of my package whereas master is the package
>> directory in GitHub?
>>
>> Am I getting it correct?
>> Is there anywhere that contains whole the process and codes in steps?
>>
>> Best regards,
>> Arman
>>
>>
>>
>>          [[alternative HTML version deleted]]
>>
>>
>> _______________________________________________
>> Bioc-devel at r-project.org mailing list
>> https://stat.ethz.ch/mailman/listinfo/bioc-devel
>>
> 
> 
> 


This email message may contain legally privileged and/or...{{dropped:2}}