From a0a9baeaddac3f18743ad52c0f463f8bb058ae04 Mon Sep 17 00:00:00 2001 From: Sean McGinnis Date: Thu, 27 Jun 2019 15:38:14 -0500 Subject: [PATCH] Retire repo This repo is no longer needed. Tools for generating the release schedule are now located in the openstack/releases repo. Change-Id: I0500fca26dc01b155c4f57097bbf2f976d13a6c8 Signed-off-by: Sean McGinnis --- CONTRIBUTING.rst | 17 --- LICENSE | 176 ------------------------- README.rst | 28 ++-- release_schedule_generator/__init__.py | 19 --- release_schedule_generator/main.py | 111 ---------------- requirements.txt | 7 - schedule.yml | 114 ---------------- setup.cfg | 28 ---- setup.py | 29 ---- 9 files changed, 10 insertions(+), 519 deletions(-) delete mode 100644 CONTRIBUTING.rst delete mode 100644 LICENSE delete mode 100644 release_schedule_generator/__init__.py delete mode 100644 release_schedule_generator/main.py delete mode 100644 requirements.txt delete mode 100644 schedule.yml delete mode 100644 setup.cfg delete mode 100644 setup.py diff --git a/CONTRIBUTING.rst b/CONTRIBUTING.rst deleted file mode 100644 index ab9927d..0000000 --- a/CONTRIBUTING.rst +++ /dev/null @@ -1,17 +0,0 @@ -If you would like to contribute to the development of OpenStack, you must -follow the steps in this page: - - http://docs.openstack.org/infra/manual/developers.html - -If you already have a good understanding of how the system works and your -OpenStack accounts are set up, you can skip to the development workflow -section of this documentation to learn how changes to OpenStack should be -submitted for review via the Gerrit tool: - - http://docs.openstack.org/infra/manual/developers.html#development-workflow - -Pull requests submitted through GitHub will be ignored. - -Bugs should be filed on Launchpad, not GitHub: - - https://bugs.launchpad.net/release-schedule-generator diff --git a/LICENSE b/LICENSE deleted file mode 100644 index 68c771a..0000000 --- a/LICENSE +++ /dev/null @@ -1,176 +0,0 @@ - - Apache License - Version 2.0, January 2004 - http://www.apache.org/licenses/ - - TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION - - 1. Definitions. - - "License" shall mean the terms and conditions for use, reproduction, - and distribution as defined by Sections 1 through 9 of this document. - - "Licensor" shall mean the copyright owner or entity authorized by - the copyright owner that is granting the License. - - "Legal Entity" shall mean the union of the acting entity and all - other entities that control, are controlled by, or are under common - control with that entity. For the purposes of this definition, - "control" means (i) the power, direct or indirect, to cause the - direction or management of such entity, whether by contract or - otherwise, or (ii) ownership of fifty percent (50%) or more of the - outstanding shares, or (iii) beneficial ownership of such entity. - - "You" (or "Your") shall mean an individual or Legal Entity - exercising permissions granted by this License. - - "Source" form shall mean the preferred form for making modifications, - including but not limited to software source code, documentation - source, and configuration files. - - "Object" form shall mean any form resulting from mechanical - transformation or translation of a Source form, including but - not limited to compiled object code, generated documentation, - and conversions to other media types. - - "Work" shall mean the work of authorship, whether in Source or - Object form, made available under the License, as indicated by a - copyright notice that is included in or attached to the work - (an example is provided in the Appendix below). - - "Derivative Works" shall mean any work, whether in Source or Object - form, that is based on (or derived from) the Work and for which the - editorial revisions, annotations, elaborations, or other modifications - represent, as a whole, an original work of authorship. For the purposes - of this License, Derivative Works shall not include works that remain - separable from, or merely link (or bind by name) to the interfaces of, - the Work and Derivative Works thereof. - - "Contribution" shall mean any work of authorship, including - the original version of the Work and any modifications or additions - to that Work or Derivative Works thereof, that is intentionally - submitted to Licensor for inclusion in the Work by the copyright owner - or by an individual or Legal Entity authorized to submit on behalf of - the copyright owner. For the purposes of this definition, "submitted" - means any form of electronic, verbal, or written communication sent - to the Licensor or its representatives, including but not limited to - communication on electronic mailing lists, source code control systems, - and issue tracking systems that are managed by, or on behalf of, the - Licensor for the purpose of discussing and improving the Work, but - excluding communication that is conspicuously marked or otherwise - designated in writing by the copyright owner as "Not a Contribution." - - "Contributor" shall mean Licensor and any individual or Legal Entity - on behalf of whom a Contribution has been received by Licensor and - subsequently incorporated within the Work. - - 2. Grant of Copyright License. Subject to the terms and conditions of - this License, each Contributor hereby grants to You a perpetual, - worldwide, non-exclusive, no-charge, royalty-free, irrevocable - copyright license to reproduce, prepare Derivative Works of, - publicly display, publicly perform, sublicense, and distribute the - Work and such Derivative Works in Source or Object form. - - 3. Grant of Patent License. Subject to the terms and conditions of - this License, each Contributor hereby grants to You a perpetual, - worldwide, non-exclusive, no-charge, royalty-free, irrevocable - (except as stated in this section) patent license to make, have made, - use, offer to sell, sell, import, and otherwise transfer the Work, - where such license applies only to those patent claims licensable - by such Contributor that are necessarily infringed by their - Contribution(s) alone or by combination of their Contribution(s) - with the Work to which such Contribution(s) was submitted. If You - institute patent litigation against any entity (including a - cross-claim or counterclaim in a lawsuit) alleging that the Work - or a Contribution incorporated within the Work constitutes direct - or contributory patent infringement, then any patent licenses - granted to You under this License for that Work shall terminate - as of the date such litigation is filed. - - 4. Redistribution. You may reproduce and distribute copies of the - Work or Derivative Works thereof in any medium, with or without - modifications, and in Source or Object form, provided that You - meet the following conditions: - - (a) You must give any other recipients of the Work or - Derivative Works a copy of this License; and - - (b) You must cause any modified files to carry prominent notices - stating that You changed the files; and - - (c) You must retain, in the Source form of any Derivative Works - that You distribute, all copyright, patent, trademark, and - attribution notices from the Source form of the Work, - excluding those notices that do not pertain to any part of - the Derivative Works; and - - (d) If the Work includes a "NOTICE" text file as part of its - distribution, then any Derivative Works that You distribute must - include a readable copy of the attribution notices contained - within such NOTICE file, excluding those notices that do not - pertain to any part of the Derivative Works, in at least one - of the following places: within a NOTICE text file distributed - as part of the Derivative Works; within the Source form or - documentation, if provided along with the Derivative Works; or, - within a display generated by the Derivative Works, if and - wherever such third-party notices normally appear. The contents - of the NOTICE file are for informational purposes only and - do not modify the License. You may add Your own attribution - notices within Derivative Works that You distribute, alongside - or as an addendum to the NOTICE text from the Work, provided - that such additional attribution notices cannot be construed - as modifying the License. - - You may add Your own copyright statement to Your modifications and - may provide additional or different license terms and conditions - for use, reproduction, or distribution of Your modifications, or - for any such Derivative Works as a whole, provided Your use, - reproduction, and distribution of the Work otherwise complies with - the conditions stated in this License. - - 5. Submission of Contributions. Unless You explicitly state otherwise, - any Contribution intentionally submitted for inclusion in the Work - by You to the Licensor shall be under the terms and conditions of - this License, without any additional terms or conditions. - Notwithstanding the above, nothing herein shall supersede or modify - the terms of any separate license agreement you may have executed - with Licensor regarding such Contributions. - - 6. Trademarks. This License does not grant permission to use the trade - names, trademarks, service marks, or product names of the Licensor, - except as required for reasonable and customary use in describing the - origin of the Work and reproducing the content of the NOTICE file. - - 7. Disclaimer of Warranty. Unless required by applicable law or - agreed to in writing, Licensor provides the Work (and each - Contributor provides its Contributions) on an "AS IS" BASIS, - WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or - implied, including, without limitation, any warranties or conditions - of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A - PARTICULAR PURPOSE. You are solely responsible for determining the - appropriateness of using or redistributing the Work and assume any - risks associated with Your exercise of permissions under this License. - - 8. Limitation of Liability. In no event and under no legal theory, - whether in tort (including negligence), contract, or otherwise, - unless required by applicable law (such as deliberate and grossly - negligent acts) or agreed to in writing, shall any Contributor be - liable to You for damages, including any direct, indirect, special, - incidental, or consequential damages of any character arising as a - result of this License or out of the use or inability to use the - Work (including but not limited to damages for loss of goodwill, - work stoppage, computer failure or malfunction, or any and all - other commercial damages or losses), even if such Contributor - has been advised of the possibility of such damages. - - 9. Accepting Warranty or Additional Liability. While redistributing - the Work or Derivative Works thereof, You may choose to offer, - and charge a fee for, acceptance of support, warranty, indemnity, - or other liability obligations and/or rights consistent with this - License. However, in accepting such obligations, You may act only - on Your own behalf and on Your sole responsibility, not on behalf - of any other Contributor, and only if You agree to indemnify, - defend, and hold each Contributor harmless for any liability - incurred by, or claims asserted against, such Contributor by reason - of your accepting any such warranty or additional liability. - diff --git a/README.rst b/README.rst index a2bb2f9..1b88a67 100644 --- a/README.rst +++ b/README.rst @@ -1,21 +1,13 @@ -======================== -Team and repository tags -======================== +This project is no longer maintained. -.. image:: http://governance.openstack.org/badges/release-schedule-generator.svg - :target: http://governance.openstack.org/reference/tags/index.html +The contents of this repository are still available in the Git +source code management system. To see the contents of this +repository before it reached its end of life, please check out the +previous commit with "git checkout HEAD^1". -.. Change things from this point on +Tools for generating a release schedule can now be found in the +openstack/releases repo. -========================== -release-schedule-generator -========================== - -Release schedule for OpenStack in YAML format - -Usage ------ - -.. code-block:: bash - - $ release-schedule-generator -o calendar-name.ics schedule.yml +For any further questions, please email +openstack-discuss@lists.openstack.org or join #openstack-dev on +Freenode. diff --git a/release_schedule_generator/__init__.py b/release_schedule_generator/__init__.py deleted file mode 100644 index 042786f..0000000 --- a/release_schedule_generator/__init__.py +++ /dev/null @@ -1,19 +0,0 @@ -# -*- coding: utf-8 -*- - -# Licensed under the Apache License, Version 2.0 (the "License"); you may -# not use this file except in compliance with the License. You may obtain -# a copy of the License at -# -# http://www.apache.org/licenses/LICENSE-2.0 -# -# Unless required by applicable law or agreed to in writing, software -# distributed under the License is distributed on an "AS IS" BASIS, WITHOUT -# WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the -# License for the specific language governing permissions and limitations -# under the License. - -import pbr.version - - -__version__ = pbr.version.VersionInfo( - 'generator').version_string() diff --git a/release_schedule_generator/main.py b/release_schedule_generator/main.py deleted file mode 100644 index 0e30241..0000000 --- a/release_schedule_generator/main.py +++ /dev/null @@ -1,111 +0,0 @@ -# Copyright (c) 2015 Louis Taylor -# -# Licensed under the Apache License, Version 2.0 (the "License"); -# you may not use this file except in compliance with the License. -# You may obtain a copy of the License at -# -# http://www.apache.org/licenses/LICENSE-2.0 -# -# Unless required by applicable law or agreed to in writing, software -# distributed under the License is distributed on an "AS IS" BASIS, -# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or -# implied. -# See the License for the specific language governing permissions and -# limitations under the License. - -import argparse -from collections import namedtuple -import datetime - -import icalendar -import yaml - - -Event = namedtuple('Event', ['name', 'description']) - - -class Week(object): - def __init__(self, date, items): - self.date = date - self.events = [] - - for event in items: - name = list(event.keys())[0] - description = event.get(name).strip() - self.events.append(Event(name, description)) - - -def description(text, cycle): - if cycle is not None: - return (text + '\n\nThis event is part of the %s OpenStack ' - 'cycle.' % cycle.capitalize()) - else: - return text - - -def make_events(week, cycle=None): - events = [] - for event_data in week.events: - event = icalendar.Event() - event.add('summary', event_data.name) - event.add('description', description(event_data.description, cycle)) - event.add('dtstart', week.date) - event.add('duration', datetime.timedelta(days=4)) - - events.append(event) - return events - - -def make_ical(schedule_content): - cal = icalendar.Calendar() - cal.add('prodid', '-//OpenStack release-schedule-generator//mxm.dk//') - cal.add('version', '2.0') - - for cycle in schedule_content: - cycle_name = cycle.get('name') - length = cycle.get('length') - release_week = cycle.get('release-week') - - release_week_names = ['R-%i' % i for i in range(0, length+1)] - - current_date = release_week - dates = {} - for name in release_week_names: - dates[name] = current_date - current_date = current_date - datetime.timedelta(days=7) - - for name in reversed(release_week_names): - events = cycle.get('events').get(name) - - if events is not None: - for calendar_entry in make_events(Week(dates[name], events), - cycle=cycle_name): - cal.add_component(calendar_entry) - return cal - - -def main(): - parser = argparse.ArgumentParser() - parser.add_argument('schedule', help='YAML file containing schedule data') - parser.add_argument('-o', '--output', - dest='ics_file', - help='name of output ical file') - args = parser.parse_args() - - with open(args.schedule) as f: - content = yaml.load(f) - - cal = make_ical(content.get('schedule')) - - if args.ics_file is not None: - ics_file = args.ics_file - else: - ics_file = 'openstack-release-schedule.ics' - - ical = cal.to_ical() - - if args.ics_file == '-': - print(ical.decode('utf-8')) - else: - with open(ics_file, 'wb') as f: - f.write(ical) diff --git a/requirements.txt b/requirements.txt deleted file mode 100644 index 7d867a0..0000000 --- a/requirements.txt +++ /dev/null @@ -1,7 +0,0 @@ -# The order of packages is significant, because pip processes them in the order -# of appearance. Changing the order has an impact on the overall integration -# process, which may cause wedges in the gate later. - -pbr>=1.6 -icalendar -pyyaml diff --git a/schedule.yml b/schedule.yml deleted file mode 100644 index f32b72e..0000000 --- a/schedule.yml +++ /dev/null @@ -1,114 +0,0 @@ ---- -schedule: - - name: mitaka - length: 24 - release-week: 2016-04-04 - - events: - R-18: - - mitaka-1: > - Dec 1-3 is the mitaka-1 milestone window for projects following the - release:cycle-with-milestones model. - R-11: - - mitaka-2: > - Jan 19-21 is the mitaka-2 milestone window for projects following - the release:cycle-with-milestones model. - R-5: - - mitaka-3: > - Libraries that are not client libraries (Oslo and others) should - issue their final release during this week. That allows to give - time for last-minute changes before feature freeze. - - Feature freeze: > - The mitaka-3 milestone marks feature freeze for projects following - the release:cycle-with-milestones model. No featureful patch should - be landed after this point. Exceptions may be granted by the - project PTL. - - Final release for client libraries: > - Client libraries should issue their final release during this week, - to match feature freeze. - - Soft StringFreeze: > - You are no longer allowed to accept proposed changes containing - modifications in user-facing strings. Such changes should be - rejected by the review team and postponed until the next series - development opens (which should happen when RC1 is published). - R-3: - - RC1 target week: > - The week of March 14-18 is the target date for projects following - the release:cycle-with-milestones model to issue their first - release candidate. - - Hard StringFreeze: > - This happens when the RC1 for the project is tagged. At this point, - ideally no strings are changed (or added, or removed), to give - translator time to finish up their efforts. - R-1: - - Final RCs and intermediary releases: > - The week of March 28 to April 1st is the last week to issue release - candidates or intermediary releases before release week. On release - week only final-release-critical releases will be accepted (at the - discretion of the release team). - R-0: - - Mitaka release: > - The Mitaka coordinated release will happen on April 7th. - - - name: newton - length: 25 - release-week: 2016-10-03 - - events: - R-23: - - Newton Design Summit: > - R-18: - - newton-1 milestone: > - May 31 - June 2 is the newton-1 milestone window for projects - following the release:cycle-with-milestones model. - R-12: - - newton-2 milestone: > - July 12-14 is the newton-2 milestone window for projects following - the release:cycle-with-milestones model. - R-6: - - Final release for non-client libraries: > - Libraries that are not client libraries (Oslo and others) should - issue their final release during this week. That allows to give - time for last-minute changes before feature freeze. - R-5: - - newton-3 milestone: > - August 30 - Sept 1 is the newton-3 milestone window for projects - following the release:cycle-with-milestones model. - - Feature freeze: > - The newton-3 milestone marks feature freeze for projects following - the release:cycle-with-milestones model. No featureful patch should - be landed after this point. Exceptions may be granted by the - project PTL. - - Final release for client libraries: > - Client libraries should issue their final release during this week, - to match feature freeze. - - Soft StringFreeze: > - You are no longer allowed to accept proposed changes containing - modifications in user-facing strings. Such changes should be - rejected by the review team and postponed until the next series - development opens (which should happen when RC1 is published). - - Requirements freeze: > - After the newton-3 milestone, only critical requirements and - constraints changes will be allowed. Freezing our requirements list - gives packagers downstream an opportunity to catch up and prepare - packages for everything necessary for distributions of the upcoming - release. The requirements remain frozen until the stable branches - are created, with the release candidates. - R-3: - - RC1 target week: > - The week of September 12 is the target date for projects following - the release:cycle-with-milestones model to issue their first - release candidate. - - Hard StringFreeze: > - This happens when the RC1 for the project is tagged. At this point, - ideally no strings are changed (or added, or removed), to give - translator time to finish up their efforts. - R-1: - - Final RCs and intermediary releases: > - The week of September 26 is the last week to issue release - candidates or intermediary releases before release week. On release - week only final-release-critical releases will be accepted (at the - discretion of the release team). - R-0: - - Newton release: > - The Newton coordinated release will happen on October 6th, 2016. diff --git a/setup.cfg b/setup.cfg deleted file mode 100644 index c2ce964..0000000 --- a/setup.cfg +++ /dev/null @@ -1,28 +0,0 @@ -[metadata] -name = release-schedule-generator -summary = Release schedule for OpenStack in YAML format -description-file = - README.rst -author = OpenStack -author-email = openstack-discuss@lists.openstack.org -home-page = http://www.openstack.org/ -classifier = - Environment :: OpenStack - Intended Audience :: Information Technology - Intended Audience :: System Administrators - License :: OSI Approved :: Apache Software License - Operating System :: POSIX :: Linux - Programming Language :: Python - Programming Language :: Python :: 2 - Programming Language :: Python :: 2.7 - Programming Language :: Python :: 3 - Programming Language :: Python :: 3.3 - Programming Language :: Python :: 3.4 - -[files] -packages = - release_schedule_generator - -[entry_points] -console_scripts = - release-schedule-generator = release_schedule_generator.main:main diff --git a/setup.py b/setup.py deleted file mode 100644 index 056c16c..0000000 --- a/setup.py +++ /dev/null @@ -1,29 +0,0 @@ -# Copyright (c) 2013 Hewlett-Packard Development Company, L.P. -# -# Licensed under the Apache License, Version 2.0 (the "License"); -# you may not use this file except in compliance with the License. -# You may obtain a copy of the License at -# -# http://www.apache.org/licenses/LICENSE-2.0 -# -# Unless required by applicable law or agreed to in writing, software -# distributed under the License is distributed on an "AS IS" BASIS, -# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or -# implied. -# See the License for the specific language governing permissions and -# limitations under the License. - -# THIS FILE IS MANAGED BY THE GLOBAL REQUIREMENTS REPO - DO NOT EDIT -import setuptools - -# In python < 2.7.4, a lazy loading of package `pbr` will break -# setuptools if some other modules registered functions in `atexit`. -# solution from: http://bugs.python.org/issue15881#msg170215 -try: - import multiprocessing # noqa -except ImportError: - pass - -setuptools.setup( - setup_requires=['pbr'], - pbr=True)