Re: [Vxl-maintainers] FW: VXL Book?

[Matt L. <mat...@ki...>]

Lianqing,

Making a tag in the svn repository for an official release is
important.  Could you please do that.  It is important because 1) we
want to know what SVN revision was used to generate the official
release, and 2) the automated scripts for building the documentation
look for that tag to determine the most recent stable release.  The
tag should be vxl-1.17.0 and tags ending with a -b are not considered
stable releases by the scripts.

In addition to the VXL homepage being way out of date, the sourceforge
download page is also out of date.  When I click the "files" tab it
says "Looking for the latest version? Download vxl-1.14.0.zip (36.0
MB)".  I was eventually able to locate a download for vxl-1.17.0, but
a new user would easily assume that 1.14.0 is the latest version.
There must be some way to indicate on the sourceforge page which
version should be considered the latest release.

Does anyone know how to updated the VXL homepage and sourceforge file
download page?  Better yet, does anyone know how and have permission
to do it?

Thanks,
Matt


On Tue, Dec 18, 2012 at 9:10 AM, YuLianqing <yu...@li...> wrote:
> Matt and Joe,
>
> The vxl-1.17.0 release is an official release and an attempt to revive the
> regular release pace of twice a year. It was precedented by two release
> candidates (may sound like beta release as the filename is post-fixed with
> letter 'b') 1.17.0-b and 1.17.0-b2. Quite a few issues in these two RCs were
> fixed before several key maintainers agreed to make a new release.
> There are two causes that may result in your misunderstanding. First, web
> pages are not updated to reflect the new release. Links in the page still
> refer to the old release and I do not know who is responsible for the
> update. Second, I am not sure if I ever made a new tag in the repository or
> not. I apologize if I forgot to do that.
>
> Lianqing
>
>> Date: Thu, 13 Dec 2012 10:40:34 -0500
>> Subject: Re: VXL Book?
>> From: mat...@ki...
>> To: mu...@le...
>> CC: yu...@li...
>
>>
>> Joe,
>>
>> If there is a subversion tag created named vxl-1.17.0 (without the -b
>> suffix), then the book will automatically update to that. If 1.17.0
>> is the official release then a package should be made available to
>> download it and the home page should be updated too.
>>
>> The script calls the following to check the tags for the latest release:
>>
>> svn list https://vxl.svn.sourceforge.net/svnroot/vxl/tags/
>>
>> --Matt
>>
>> On Thu, Dec 13, 2012 at 10:06 AM, Joseph Mundy <mu...@le...>
>> wrote:
>> > Matt,
>> > It seems that the 1.17 version is good to go. It was built successfully
>> > recently on a lot of platforms in a project we are involved in. Maybe
>> > Lianqing Yu can move it to the official "latest release" I assume then
>> > the
>> > book will follow?
>> > Thanks,
>> > Joe
>> >
>> > -----Original Message-----
>> > From: Matt Leotta [mailto:mat...@ki...]
>> > Sent: Thursday, December 13, 2012 9:44 AM
>> > To: Joseph Mundy
>> > Subject: Re: VXL Book?
>> >
>> > Joe,
>> >
>> > The vpgl chapter does appear under the "Current development version (SVN
>> > snapshot)" link:
>> >
>> >
>> > http://public.kitware.com/vxl/doc/development/books/core/book_14.html#SEC173
>> >
>> > It does not appear under the "Latest Release". The latest release is
>> > determined automatically by looking and SVN version tags. The greatest
>> > release version is selected that does not end with a '-b*'
>> > (presumably these are beta releases). Currently the latest release tag
>> > is
>> > vxl-1.14.0, which is almost 2 years old. There is a vxl-1.17.0-b tag,
>> > but
>> > that is assumed to be a beta release by the script. It seems vxl-1.17.0
>> > was
>> > never officially released either by creating a SVN tag or by uploading
>> > the
>> > zip file. The current downloadable version is vxl-1.14.0 (though the
>> > home
>> > page states 1.13.0).
>> >
>> > It seems efforts to maintain regular releases of VXL have died off.
>> > Somewhat understandable given the maintenance headache for such a large
>> > subversion repository. Recently many other repositories including
>> > OpenCV,
>> > FFMPEG, and all of Kitware's software have migrated to git for version
>> > control. This makes release management much easier. I made a push a
>> > while
>> > back for VXL to take this direction, but there was strong resistance
>> > from
>> > Peter and mild resistance from a few other key developers.
>> >
>> > --Matt
>> >
>> > On Wed, Dec 12, 2012 at 5:23 PM, Joseph Mundy <mu...@le...>
>> > wrote:
>> >> Matt,
>> >>
>> >> I noticed that the vpgl chapter doesn't appear in the current version
>> >> of the VXL book hosted by Kitware. However it is checked in.
>> >>
>> >> What's up?
>> >>
>> >> Thanks,
>> >>
>> >> Joe
>> >
>
> ------------------------------------------------------------------------------
> LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial
> Remotely access PCs and mobile devices and provide instant support
> Improve your efficiency, and focus on delivering more value-add services
> Discover what IT Professionals Know. Rescue delivers
> http://p.sf.net/sfu/logmein_12329d2d
> _______________________________________________
> Vxl-maintainers mailing list
> Vxl...@li...
> https://lists.sourceforge.net/lists/listinfo/vxl-maintainers
>