# 1.12 development timeline

**URL:** <https://discourse.openrobotics.org/t/1-12-development-timeline/8166>\
**Category:** Autoware\
**Created:** [March 6, 2019, 5:10am UTC](https://discourse.openrobotics.org/t/1-12-development-timeline/8166 "2019-03-06T05:10:52Z")\
**Posts on this page:** 1\
**Showing post:** 1

<div class="post-metadata">

**Author:** ![gbiggs](https://sea2.discourse-cdn.com/flex022/user_avatar/discourse.openrobotics.org/gbiggs/32/30361_2.png) [@gbiggs](https://discourse.openrobotics.org/u/gbiggs)\
**Post date:** [March 6, 2019, 5:10am UTC](https://discourse.openrobotics.org/t/1-12-development-timeline/8166/1 "2019-03-06T05:10:53Z")

</div>

This thread is to plan the work to be done in the first couple of weeks of the 1.12 release cycle.

Because we are planning some significant changes to our development processes and environment for 1.12, we need to decide what will be done when to prevent problems such as PRs being made while we are moving packages around.

This is the list of things that need to be done, not necessarily in order. Please comment if you think I have missed one.

- Move the `Autoware` reposiory to the `autowarefoundation` organisation
- Create new repositories according to the [repository discussion](http://discourse.ros.org/t/splitting-the-autoware-ai-repository-and-changing-the-organisation/8139)
- Move packages to new repositories
- Move packages to new layout
- Change permissions on repository
- Add `.repos` file and switch to using `vcs` for installation
- Decided on features to include in 1.12 and add them to the milestone
- Clean up the branches to match the [new branching model](https://github.com/CPFL/Autoware/wiki/Contributing-to-Autoware.AI#repository-guidelines)
- Fixing CI to work with the new repository layout
- Fix the docker images

Here is my proposal for when we do each thing that needs to be done. Please comment and I will update the table as we discuss.

| Day | Things to do |
| --- | --- |
| Thursday, March 21 | Release 1.11 |
| | Start of no-new-PRs period |
| Friday, March 22 | Public holiday |
| Saturday, March 23 | |
| Sunday, March 24 | Sleep |
| Monday, March 25 | Move the repository to the new organisation |
| | Create new repositories for Autoware |
| | Change permissions on repositories |
| | Create `autoware.repos` |
| | Change installation instructions to use `vcs` |
| | Remove `develop` branch; master becomes the main branch |
| | Start collecting features for 1.12 |
| Tuesday, March 26 | Start fixing CI and docker |
| | Clean up other branches as possible |
| Wednesday, March 27 | |
| Thursday, March 28 | |
| Friday, March 29 | |
| Saturday, March 30 | |
| Sunday, March 31 | Sleep more |
| Monday, April 1 | Freeze list of features targeted for 1.12 (except for justified exceptions on a case-by-case basis) |
| | Contributors start working on their own fork |
| | Open for PRs again |
| Tuesday, April 2 | |
| Wednesday, April 3 | |
| Some time during the above | Fix CI to match new repositories |
| After | Move packages one at a time to new repositories (timing of each based on PRs for that package) |
| | Move code between packages to improve package layout |

Ultimately, this work is going to be disruptive. My hope is that by doing it as soon as possible and in one chunk we can minimise that disruption.

I think the package reorganisation (into repositories, and code into packages) can be done over  
time. We can do each package individually once we shift to `vcs` so there is no need to rush them  
all in at once. This gives us some flexibility to work around pull requests.

An open question is what to do with existing PRs that won’t be merged for 1.11. Do we ask the  
person doing it to move to a fork and make a new PR now?

**Update 2019/03/12**  
We can move the repository to a new organisation and keep all the issues, watchers, stars, etc. I have updated the schedule.

**Update 2019/03/15**  
Delayed everything a week due to the delay in releasing 1.11.

---

_[View the full topic](https://discourse.openrobotics.org/t/1-12-development-timeline/8166)._