4:11 a.m.
Ahoy, now that Travis is happy with the master branch from the
quickstarts[1]. I would like to confirm the flow for development.
I was thinking about merge to 'latest' the changes from master only after
the Keycloak release and we keep submitting PRs to master.
Does it make any sense?
[1] - https://travis-ci.org/keycloak/keycloak-quickstarts/builds/235530549
11:01 a.m.
Works for me !
On Wed, May 24, 2017 at 11:11 AM, Bruno Oliveira <bruno(a)abstractj.org>
wrote:
Ahoy, now that Travis is happy with the master branch from the
quickstarts[1]. I would like to confirm the flow for development.
I was thinking about merge to 'latest' the changes from master only after
the Keycloak release and we keep submitting PRs to master.
Does it make any sense?
[1] - https://travis-ci.org/keycloak/keycloak-quickstarts/builds/235530549
_______________________________________________
keycloak-dev mailing list
keycloak-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/keycloak-dev
2:29 a.m.
Why not just do it at the same time as a release? The Keycloak release
server could:
* Release Keycloak
* Bump version in quickstarts master
* Pull in changes from master to latest
* Bump version in quickstart master to next SNAPSHOT
That does require CI job that runs master branch to make sure it works with
latest SNAPSHOT though.
On 24 May 2017 at 11:11, Bruno Oliveira <bruno(a)abstractj.org> wrote:
Ahoy, now that Travis is happy with the master branch from the
quickstarts[1]. I would like to confirm the flow for development.
I was thinking about merge to 'latest' the changes from master only after
the Keycloak release and we keep submitting PRs to master.
Does it make any sense?
[1] - https://travis-ci.org/keycloak/keycloak-quickstarts/builds/235530549
_______________________________________________
keycloak-dev mailing list
keycloak-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/keycloak-dev
9:47 a.m.
My question was related with the daily basis dev flow and yes, we need to
automate this. To not miss what you mentioned I created this jira:
https://issues.jboss.org/browse/KEYCLOAK-4982
On Mon, May 29, 2017 at 4:29 AM Stian Thorgersen <sthorger(a)redhat.com>
wrote:
Why not just do it at the same time as a release? The Keycloak
release
server could:
* Release Keycloak
* Bump version in quickstarts master
* Pull in changes from master to latest
* Bump version in quickstart master to next SNAPSHOT
That does require CI job that runs master branch to make sure it works
with latest SNAPSHOT though.
On 24 May 2017 at 11:11, Bruno Oliveira <bruno(a)abstractj.org> wrote:
> Ahoy, now that Travis is happy with the master branch from the
> quickstarts[1]. I would like to confirm the flow for development.
>
> I was thinking about merge to 'latest' the changes from master only after
> the Keycloak release and we keep submitting PRs to master.
>
> Does it make any sense?
>
> [1] -
> https://travis-ci.org/keycloak/keycloak-quickstarts/builds/235530549
>
_______________________________________________
> keycloak-dev mailing list
> keycloak-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/keycloak-dev
>
2538
days inactive
2543
days old
3 comments
3 participants
participants (3)
-
Bruno Oliveira -
Sebastien Blanc -
Stian Thorgersen