Comments (20)
I think we had no real choice if we want have a better quality of software. So normal user can run the stable branch and other can use the rc branch. For hass.io user it will ve a simple button to move around.
from architecture.
It's exactly the same pace, the names are just changed.
from architecture.
I believe there is an eager amount of users who are not coders and are willing to test rc.
from architecture.
It's only 3 weeks when we introduce it. The RC period is still overlapping with the first week of the 2 week release cycle, thus after that it's just every 2 weeks again.
from architecture.
For the documentation: I've switched the website to use Netlify. This means now that any PR and branch will have their own builds. That means that people can already browse the docs for the RC without it being live on the main website.
from architecture.
We'll have the following tasks to achieve this:
- Contact netlify to get subdomains for
rc
andnext
branches (in progress) - Script to automatically cherry-pick new tagged and merged PRs into the
rc
branch, update version number (ie0.65.0.rc3
->0.65.0.rc4
), publish to PyPi. Docker will automatically build this branch. - Hass.io automatic builds off the
rc
branch - Script to automatically merge
dev
intorc
branch for code cut off for both main and docs website.
from architecture.
So master will then have a three week release cycle, instead of two, right?
Sounds good, 👍.
from architecture.
Correct.
from architecture.
Can we push the rc also as pre-release to https://github.com/home-assistant/home-assistant/releases ? That make it easier to follow up and for automatic builds.
from architecture.
Yes, we will do that.
from architecture.
Do we rollout this with 0.66 or 0.67 ?
from architecture.
I was thinking about 0.66. Do you have any objections for it to be that early?
from architecture.
Who will use the rc that isn't running dev today? It sounds that you'll lower release pace and not really gain anything except take longer to reach the mass you need to get proper feedback.
from architecture.
Getting a build published to PyPI, Hass.io and Docker makes it way more accessible to test than dev.
from architecture.
But is it worth a 50% decrease in speed? It's still a loss in feedback
from architecture.
@armills is correct. Take 0.65 as an example, 0.65.0 would have been published as 0.65.0.rc0. Then 0.65.5 would have been 0.65.0.rc5 and would have been promoted to 0.65.0 tomorrow.
from architecture.
I understand that for the rc. Let's hope most users go that route. But for people going for stable there is a 3 week pace and if I understand it correctly bugs on stable will take 3 weeks to reach users. So is there really any benefit to separate stable?
from architecture.
I understand it better now. Thanks
from architecture.
@balloob
I have slowed down page loading speed after website switched to netlify. Seems CDN by netlify not working, all access to https://home-assistant.io/
pointed to server in US. https://home-assistant-docs.netlify.com/
load much faster on my ISP.
Not sure CNAME flattening from Cloudflare works correctly or not.
from architecture.
Alright, we're trying this out: https://www.home-assistant.io/blog/2018/03/24/new-release-schedule/
from architecture.
Related Issues (20)
- Splitting tests files in smaller files in components/modules tests HOT 1
- Feature Request HOT 1
- Add favorite position to Cover entity HOT 10
- Add feature light distribution control to LightEntity
- Add new CURRENT_HVAC constants HOT 1
- Add Home Appliance entity
- Officially allow enities to set their entity ID not based on their names HOT 2
- Custom Device Class for Binary Sensors HOT 9
- Installed homeassistant supervised on my Linux machine; can't get it to run. HOT 1
- Expand enqueue options media player HOT 2
- Extend Rest API - unique_id HOT 3
- Add "status" as an attribute to CalendarEvents HOT 5
- Add list of (upcoming) calendar events to templating HOT 1
- Creating automations on the fly HOT 1
- Optional health check HOT 2
- Open letter for improving Home Assistant's Authentication system HOT 7
- Add device_class Heater HOT 2
- Area Units HOT 3
- New Device class for Reactive Energy (varh) HOT 1
- "Lost" device HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from architecture.