[Bioc-devel] Committing changes to the release branch

Patrick Aboyoun paboyoun at fhcrc.org
Thu Apr 29 18:29:49 CEST 2010

I was looking into this issue and found it was a typo that was 
propagated throughout the svn permissions file. Please try committing 
your changes to the BioC 2.6 branch again. Sorry for the inconvenience.


On 4/29/10 6:55 AM, Seth Falcon wrote:
> Hi,
> First, we will investigate the svn permission issues this morning and
> things going again.
> On 4/29/10 6:34 AM, Kasper Daniel Hansen wrote:
>> At this point I would like to highlight the final step on the Bioc
>> HOWTO for updating the release branch:
>> "Send a mail to the main bioconductor email list to announce the new version."
>> It seems almost no-one - including the Biocore team - follows this.
>> Should this requirement be removed (I don't think so personally, but
>> since it is not adhered to, there is not much point in having it)?
> This doesn't strike me as a very fair assessment.  In many cases,
> changes are initiated due to discussion on the list and these threads
> are often resolved with a "fixed in release and devel available in
> 36hrs" sort of message.
> In any case, sending an email to the Bioconductor list to announce
> changes to release packages seems like a useful idea.  I would encourage
> folks to follow it.
> + seth
> _______________________________________________
> Bioc-devel at stat.math.ethz.ch mailing list
> https://stat.ethz.ch/mailman/listinfo/bioc-devel

More information about the Bioc-devel mailing list