[DVDnav-discuss] New release planned? Yes!

[Timothy Gu]

On Nov 4, 2013 11:20 AM, "Roger Pack" <rogerdpack2 at gmail.com> wrote:
>
> On 10/31/13, Erik Hovland <erik at hovland.org> wrote:
> > On Thu, Oct 31, 2013 at 12:48 PM, Roger Pack <rogerdpack2 at gmail.com>
wrote:
> >> On 10/29/13, Paul Menzel <paulepanter at users.sourceforge.net> wrote:
> >>> Dear Timothy,
> >>>
> >>>
> >>> Am Sonntag, den 27.10.2013, 18:06 -0700 schrieb Timothy Gu:
> >>>
> >>>> It's quite some time before the last release. There are some critical
> >>>> security fixes in SVN now. I guess it should be time for a new
release.
> >>>
> >>> before sending a message next time, please take the time to at least
> >>> look through the list archives of the last two months. Then you would
> >>> have found the thread [1]
> >>>
> >>>     [DVDnav-discuss] new release, call for patches
> >>>
> >>> and you would have known that a release is indeed.
> >>>
> >>>> Also, if possible, can someone back port changes in the VideoLAN's
fork
> >>>> to
> >>>> the official one?
> >>>
> >>> Not until somebody sends the patches to the list for review. It would
be
> >>> great if you could do it. `git format-patch` and `git send-email`
should
> >>> help with this.
> >>
> >> The main repo is subversion, isn't it, though?
> >
> > It is. But our development trees will gladly accept patches from git
> > sent by email. Is anyone using straight subversion for their
> > day-to-day development? I have been using git-svn for some time now.
>
> (of course, as previously stated, my personal preference would be to
> have the main repo in git/github as well, as stated before...)

Yes, preferably have the repo in GitHub. GitHub now is the de facto
standard for FOSS development (like several years earlier SourceForge was),
and Git is a really nice VCS that is a generation ahead of SVN. GitHub pull
request is a really convenient way to send patches. With that in mind, it
would also be easier for other projects to integrate libdvdread/nav to
their own application through submodules and things like that, and also
easier for us to merge VLC changes if we will.

Timothy