Per best practices, explicitly use the python3 executable rather than
assuming the platform with have a "python" executable that maps to
python3.
https://www.python.org/dev/peps/pep-0394/
Change-Id: I39b8a1013a891f4570f374d8faa3cfa2ecaf3347
Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com>
Change I3cc38afd80eb41200c7269a3039e87f01156eaab switched this tool to
generate a yaml file for driving the release schedule page. That also
removed the ability to generate an etherpad formatted output, but the
option was not removed. This cleans up the unused option.
Change-Id: I2e1b8dcb92239e891ac27af8a503f901c835c808
Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com>
Instead of building the RST table, build a YAML input data file to be
used with the new schedule rendering template. The results will have to
be edited by hand, but we at least get the dates and fixed events
included for free.
Change-Id: I3cc38afd80eb41200c7269a3039e87f01156eaab
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
As per OpenStack licensing guide lines [1]:
[H102 H103] Newly contributed Source Code should be licensed under
the Apache 2.0 license.
[H104] Files with no code shouldn't contain any license header nor
comments, and must be left completely empty.
[1] http://docs.openstack.org/developer/hacking/#openstack-licensing
Change-Id: I9f4673f19ce045a2aad656fdc27679a8ada23ff7
The release schedule is no longer bounded by the summit, so don't
include it.
Add 2 weeks for the cycle-trailing deadline.
Change-Id: I8bca376d910c218b65a29d2e400fd519348f73b9
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
Add an output option for building the schedule planning calendar
etherpad.
Change-Id: I3be5d94a1cb243a8d9e601b51959a1d97ba93083
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
Add a tool to produce the schedule table, and add a table for newton's
schedule based on when the summit is and the three week period we have
for mitaka between the release and the newton summit.
Change-Id: I4a4a16426b00c5f21a10d0ce9de221d588ee5fe5
Signed-off-by: Doug Hellmann <doug@doughellmann.com>