1. 29 Oct, 2017 1 commit
  2. 09 Sep, 2017 1 commit
  3. 20 Aug, 2017 1 commit
  4. 19 Aug, 2017 1 commit
  5. 18 Jul, 2017 1 commit
  6. 25 Jun, 2017 1 commit
  7. 11 Jun, 2017 1 commit
  8. 20 Mar, 2017 1 commit
  9. 12 Mar, 2017 1 commit
  10. 26 Jan, 2017 1 commit
  11. 18 Jan, 2017 2 commits
    • Sébastien Wilmet's avatar
      News: add news for release 3.22.1 · 060081a8
      Sébastien Wilmet authored
      The release was created in a side-branch. From now on, I'll try to keep
      the NEWS file complete on the master branch, to have a good history
      overview.
      060081a8
    • Sébastien Wilmet's avatar
      Add release dates to the NEWS file · 94e43692
      Sébastien Wilmet authored
      I think it's useful information. It can be retrieved from git, but to do
      it correctly (get the commiter date of the commit that the git tag
      points to) is more difficult. It's easier if it's present in the NEWS
      file.
      
      The dates have been added with this quick and dirty script:
      ```
      	#!/usr/bin/env bash
      
      	tags_list=`git tag`
      	for tag in $tags_list
      	do
      		# For the date, it takes the commiter date of the git commit that $tag
      		# points to. This is normally the closest date to the real date of the
      		# release (if the tag refers to a version). Sometimes a maintainer
      		# forgets to create the tag and the tag is created afterwards.
      		#
      		# To show git tags alongside the tag creation dates, use the following
      		# command instead:
      		# $ git tag -l --format="%(refname:strip=2) - %(taggerdate:short)"
      
      		commiter_date=`git log -1 --date=short --pretty="format:%cd" $tag`
      
      		sed -i "s/^\(Release ${tag#v}\)$/\1, ${commiter_date}/" NEWS
      	done
      
      	sed -i "s/\(--------\)/\1------------/" NEWS
      ```
      
      For the versions <= 0.2, the dates have been added manually from the
      information in the first git repo (no longer public).
      94e43692
  12. 18 Sep, 2016 1 commit
  13. 29 Jul, 2016 1 commit
  14. 20 Mar, 2016 1 commit
  15. 13 Mar, 2016 1 commit
  16. 15 Feb, 2016 1 commit
  17. 17 Jan, 2016 1 commit
  18. 13 Dec, 2015 1 commit
  19. 23 Nov, 2015 1 commit
  20. 08 Nov, 2015 1 commit
  21. 14 Oct, 2015 1 commit
  22. 01 Oct, 2015 1 commit
  23. 23 Jul, 2015 1 commit
  24. 25 Mar, 2015 1 commit
  25. 09 Jan, 2015 1 commit
  26. 26 Oct, 2014 1 commit
  27. 01 Oct, 2014 1 commit
  28. 22 Sep, 2014 1 commit
    • Sébastien Wilmet's avatar
      Release 3.14.0 - Pi version! · c1a617c5
      Sébastien Wilmet authored
      It's easier to follow GNOME versions. For the packagers, for the users,
      for the contributors, and for the maintainers. When creating a
      latexila-x-y branch, a mail must be manually sent to the GNOME
      translation and documenation teams, which is not convenient. On the
      other hand, when creating a gnome-x-y branch, mails are sent
      automatically.
      
      The 2.0 version was chosen because there was a major code change (a
      complete rewrite). But now only incremental changes are made every six
      months.
      c1a617c5
  29. 26 Mar, 2014 1 commit
  30. 16 Feb, 2014 1 commit
  31. 01 Nov, 2013 1 commit
  32. 11 Oct, 2013 1 commit
  33. 31 Aug, 2013 1 commit
  34. 07 Jun, 2013 1 commit
  35. 06 May, 2013 1 commit
  36. 28 Mar, 2013 1 commit
  37. 22 Jan, 2013 1 commit
  38. 24 Nov, 2012 1 commit
  39. 19 Oct, 2012 1 commit