How to find out what changed in a release
Hi, I am looking at the ChangeLog in the tarball for the latest release 1.2.5.3, and it doesn't have an entry. Plus I also noticed the last two entries (1.2.5.2 and 1.2.5.1) in the ChangeLog also just say 'Maintenance release/bug fixes'. So how would I find out what has changed, i.e. which bugs have been fixed in each release? Regards, -- Craig
I would use Fisheye for this. The devs are really good at using the "--resolved FS-xxxx" syntax when doing git commits. Look at the commits leading up to 1.2.5.3 being tagged and you'll see which bugs specifically were addressed. -MC On Mon, Dec 10, 2012 at 2:56 PM, Craig Ayliffe <cayliffe@gmail.com> wrote:
Hi,
I am looking at the ChangeLog in the tarball for the latest release 1.2.5.3, and it doesn't have an entry. Plus I also noticed the last two entries (1.2.5.2 and 1.2.5.1) in the ChangeLog also just say 'Maintenance release/bug fixes'.
So how would I find out what has changed, i.e. which bugs have been fixed in each release?
Regards,
-- Craig
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
FreeSWITCH-powered IP PBX: The CudaTel Communication Server http://www.cudatel.com
Official FreeSWITCH Sites http://www.freeswitch.org http://wiki.freeswitch.org http://www.cluecon.com
FreeSWITCH-dev mailing list FreeSWITCH-dev@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-dev UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-dev http://www.freeswitch.org
-- Michael S Collins Twitter: @mercutioviz http://www.FreeSWITCH.org http://www.ClueCon.com http://www.OSTAG.org
If you have the source tree checked out with git, git log can be used to print what happened between tags as well. It's been something I been meaning to revisit but never seem to get to. For tarball releases, Fisheye like suggested above would be the easiest. On Mon, Dec 10, 2012 at 6:22 PM, Michael Collins <msc@freeswitch.org> wrote:
I would use Fisheye for this. The devs are really good at using the "--resolved FS-xxxx" syntax when doing git commits. Look at the commits leading up to 1.2.5.3 being tagged and you'll see which bugs specifically were addressed.
-MC
On Mon, Dec 10, 2012 at 2:56 PM, Craig Ayliffe <cayliffe@gmail.com> wrote:
Hi,
I am looking at the ChangeLog in the tarball for the latest release 1.2.5.3, and it doesn't have an entry. Plus I also noticed the last two entries (1.2.5.2 and 1.2.5.1) in the ChangeLog also just say 'Maintenance release/bug fixes'.
So how would I find out what has changed, i.e. which bugs have been fixed in each release?
Regards,
-- Craig
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
FreeSWITCH-powered IP PBX: The CudaTel Communication Server http://www.cudatel.com
Official FreeSWITCH Sites http://www.freeswitch.org http://wiki.freeswitch.org http://www.cluecon.com
FreeSWITCH-dev mailing list FreeSWITCH-dev@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-dev UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-dev http://www.freeswitch.org
-- Michael S Collins Twitter: @mercutioviz http://www.FreeSWITCH.org http://www.ClueCon.com http://www.OSTAG.org
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
FreeSWITCH-powered IP PBX: The CudaTel Communication Server http://www.cudatel.com
Official FreeSWITCH Sites http://www.freeswitch.org http://wiki.freeswitch.org http://www.cluecon.com
FreeSWITCH-dev mailing list FreeSWITCH-dev@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-dev UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-dev http://www.freeswitch.org
participants (3)
-
Craig Ayliffe
-
Michael Collins
-
William Suffill