[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Libcdio-devel] RFC: Two releases or one?
From: |
Rocky Bernstein |
Subject: |
Re: [Libcdio-devel] RFC: Two releases or one? |
Date: |
Mon, 20 Feb 2012 17:56:32 -0500 |
On Mon, Feb 20, 2012 at 5:23 PM, Nicolas Boullis <address@hidden>wrote:
> Hi,
>
> On Mon, Feb 20, 2012 at 07:45:15AM -0500, Rocky Bernstein wrote:
> > There have a few larger unrelated changes that taken place and I would
> like
> > to solicit opinions on whether we should have one release with all of the
> > changes or two?
> >
> > The changes are
> >
> > * CD-Text completion (some incompatibility)
>
> Just curious, why these incompatibilities?
>
The new cdtext_get() adds a parameter for the track. I suppose we could
have and added a new routine rather than modify the old one in an
incompatible way.
I don't have strong feelings on this. Perhaps Leon could comment.
>
> > * UDF improvement and header reworking for Microsoft OS's
> > * Removal of cd-paranoia which is be in now in a separate GPL v2+
> directory
> > * Various bug fixes
> >
> > Comments?
>
> If you make two releases, do you know what would be in which release?
>
I had considered one branch having
* paranoia removed
* cd-text changes
* whatever compatible UDF/Joliet/Rock Ridge fixes
And in another the incompatible header changes plus whatever the
UDF/Joliet/Rock Ridge changes aren't
in the first release.
Does it mean you would consider having 2 branches for libcdio?
>
There already is a pbatard branch.
>
>
> Cheers,
>
> --
> Nicolas
>
>
Re: [Libcdio-devel] RFC: Two releases or one?, Nicolas Boullis, 2012/02/20
- Re: [Libcdio-devel] RFC: Two releases or one?,
Rocky Bernstein <=