Contents

###
# use period for season? why? why not? 
#   - semantic hairsplitting?  make it an alias? why? why not? who cares?


###
# use 2012-13 or 2012_13  or 2012.13 or 2012+13  why? why not ???

2020/21
2019/20
2018/19
2017/18
2016/17
2015/16
2014/15
2013/14
2012/13
2011/12
2010/11
2009/10
2008/09
2007/08
2006/07
2005/06
2004/05
2003/04
2002/03
2001/02
2000/01

# -- years only -- 

2022
2021
2020
2019
2018
2017
2016
2015
2014
2013
2012
2011
2010
2009
2008
2007
2006
2005
2004
2003
2002
2001
2000


# e.g. Liga MX has two (complete) seasons in *one* year e.g. Clausura 2013 n Apertura 2013
### for 2013.1  use 2013_I 2013-I 2013.I n 2013-II 2013.II or 2013.A n 2013.B - why? why not??

2015.1
2015.2
2014.1
2014.2
2013.1
2013.2
2012.1
2012.2
2011.1
2011.2
2010.1
2010.2

Version data entries

51 entries across 51 versions & 2 rubygems

Version	Path
sportdb-models-1.18.0	data/seasons.txt
sportdb-models-1.17.0	data/seasons.txt
sportdb-models-1.16.2	data/seasons.txt
sportdb-models-1.16.1	data/seasons.txt
sportdb-models-1.16.0	data/seasons.txt
sportdb-models-1.15.2	data/seasons.txt
sportdb-models-1.15.1	data/seasons.txt
sportdb-models-1.15.0	data/seasons.txt
sportdb-models-1.14.2	data/seasons.txt
sportdb-models-1.14.1	data/seasons.txt
sportdb-models-1.14.0	data/seasons.txt
sportdb-models-1.13.0	data/seasons.txt
sportdb-models-1.12.0	data/seasons.txt
sportdb-models-1.11.2	data/seasons.txt
sportdb-models-1.11.1	data/seasons.txt
sportdb-models-1.11.0	data/seasons.txt
sportdb-models-1.10.1	data/seasons.txt
sportdb-models-1.10.0	data/seasons.txt
sportdb-1.9.16	data/seasons.txt
sportdb-1.9.15	data/seasons.txt