We have moved to a new Sailfish OS Forum. Please start new discussions there.
1 | initial version | posted 2015-02-03 15:47:03 +0200 |
We've been testing pushing early updates to a small group of opt-in users for update9 and the connectivity hotfix. This went well so we're going one step further and making each software update available for opt in approximately one week before releasing it. We mainly expect this to be useful for developers and technically minded users who can handle potential problems (eg if you don't know how to do a backup and a restore then it may not be for you)
We hope this is a step towards more community integration into our release process. This helps us to improve quality by identifying critical issues which only show up in certain environments or device setups before rolling the update out to the larger crowd. As an added bonus it provides a window for developers to test their applications on new releases.
In the long term it should help us to establish a developer program with early release candidate access for registered developers, and to have more community involvement in platform development.
The first detail we're hoping to learn from this is how can we gather feedback from a large audience in a reasonable way.
2 | retagged |
We've been testing pushing early updates to a small group of opt-in users for update9 and the connectivity hotfix. This went well so we're going one step further and making each software update available for opt in approximately one week before releasing it. We mainly expect this to be useful for developers and technically minded users who can handle potential problems (eg if you don't know how to do a backup and a restore then it may not be for you)
We hope this is a step towards more community integration into our release process. This helps us to improve quality by identifying critical issues which only show up in certain environments or device setups before rolling the update out to the larger crowd. As an added bonus it provides a window for developers to test their applications on new releases.
In the long term it should help us to establish a developer program with early release candidate access for registered developers, and to have more community involvement in platform development.
The first detail we're hoping to learn from this is how can we gather feedback from a large audience in a reasonable way.
3 | No.3 Revision |
We've been testing pushing early updates to a small group of opt-in users for update9 and the connectivity hotfix. This went well so we're going one step further and making each software update available for opt in approximately one week before releasing it. We mainly expect this to be useful for developers and technically minded users who can handle potential problems (eg if you don't know how to do a backup and a restore then it may not be for you)
We hope this is a step towards more community integration into our release process. This helps us to improve quality by identifying critical issues which only show up in certain environments or device setups before rolling the update out to the larger crowd. As an added bonus it provides a window for developers to test their applications on new releases.
In the long term it should help us to establish a developer program with early release candidate access for registered developers, and to have more community involvement in platform development.
The first detail we're hoping to learn from this is how can we gather feedback from a large audience in a reasonable way.
4 | No.4 Revision |
We've been testing pushing early updates to a small group of opt-in users for update9 and the connectivity hotfix. This went well so we're going one step further and making each software update available for opt in approximately one week before releasing it. We mainly expect this to be useful for developers and technically minded users who can handle potential problems (eg if you don't know how to do a backup and a restore then it may not be for you)
We hope this is a step towards more community integration into our release process. This helps us to improve quality by identifying critical issues which only show up in certain environments or device setups before rolling the update out to the larger crowd. As an added bonus it provides a window for developers to test their applications on new releases.
In the long term it should help us to establish a developer program with early release candidate access for registered developers, and to have more community involvement in platform development.
The first detail we're hoping to learn from this is how can we gather feedback from a large audience in a reasonable way.
We've been testing pushing early updates to a small group of opt-in users for update9 and the connectivity hotfix. This went well so we're going one step further and making each software update available for opt in approximately one week before releasing it. We mainly expect this to be useful for developers and technically minded users who can handle potential problems (eg if you don't know how to do a backup and a restore then it may not be for you)
We hope this is a step towards more community integration into our release process. This helps us to improve quality by identifying critical issues which only show up in certain environments or device setups before rolling the update out to the larger crowd. As an added bonus it provides a window for developers to test their applications on new releases.
In the long term it should help us to establish a developer program with early release candidate access for registered developers, and to have more community involvement in platform development.
The first detail we're hoping to learn from this is how can we gather feedback from a large audience in a reasonable way.
6 | No.6 Revision |
We've Early access has been testing pushing early updates to a small group of opt-in users for update9 and the connectivity hotfix. This went well so we're going one step further and making each software update available for opt in approximately one week very successful program in the Sailfish community since we launched it in 2015. It has helped us find certain bugs with the community's help before releasing it. We mainly expect each update to the masses, and has also greatly improved how our community impacts our software releasing speed and quality.
With the release of Sailfish 3, we are committed to continue this program.
The early access programme is still very much intended to be useful for developers and used by technically minded users who can handle potential problems (eg if you don't know how to do a backup and a restore then it may not be for you)
We hope this is a step towards more community integration into our release process. This helps us to improve quality by identifying critical issues which only show up in certain environments or device setups before rolling the update out to the larger crowd. As an added bonus it provides a window for developers to test their applications on new releases.
In the long term it should help us to establish a developer program with early release candidate access for registered developers, and to have more community involvement in platform development.
The first detail we're hoping to learn from this is how can we gather feedback from a large audience in a reasonable way.problems.
Happy updating!