I have just changed the class definition for a core class in bsseq. A
supporting experiment data package, bsseqData, contains two objects of this
core class and now it needs to be updated (specifically because the
example() contains a command which prints the object and this printing now
fails).
On Wed, Jul 10, 2013 at 7:05 AM, Kasper Daniel Hansen
wrote:
> I have just changed the class definition for a core class in bsseq. A
> supporting experiment data package, bsseqData, contains two objects of this
> core class and now it needs to be updated (specifically because the
> example() cont
This will help me branch code, but not objects with changed definitions.
Kasper
On Wed, Jul 10, 2013 at 12:44 PM, Dan Tenenbaum wrote:
> On Wed, Jul 10, 2013 at 7:05 AM, Kasper Daniel Hansen
> wrote:
> > I have just changed the class definition for a core class in bsseq. A
> > supporting exp
On Wed, Jul 10, 2013 at 10:51 AM, Kasper Daniel Hansen
wrote:
> This will help me branch code, but not objects with changed definitions.
>
Can you store two separate objects, one that's 2.12-compatible and the
other newer?
After the next release, when we stop building 2.12, this will become
unne
It's simpler than that. Just make the change you need to make.
The package will fail to pass the build/check in release so it
won't propagate.
That means that whatever version of bsseqData is currently in
BioC 2.12 will remain forever i.e. you won't be able to update
it. Hope that's OK with you.
Thanks, this is very helpful. In general, following our release paradigm,
I see no reason to ever want to update bsseqData for Bioconductor 2.12 -
since it is a data package chances are small for finding a critical bug.
Best,
Kasper
On Wed, Jul 10, 2013 at 3:17 PM, Hervé Pagès wrote:
> It's s
I had this issue with GWASTools/GWASdata at one point. There is only
one copy of an experiment data package, so if you change it, it will
break the current release version of bsseq. The solution I came up with
was to add new objects with different names to the data package, and
change my exam
Hi Stephanie,
On 07/10/2013 12:51 PM, Stephanie M. Gogarten wrote:
I had this issue with GWASTools/GWASdata at one point. There is only
one copy of an experiment data package, so if you change it, it will
break the current release version of bsseq.
Yes there is only one copy of an experiment
