Thanks Daniel and Bruno.
I'd say that the release process is fine expect committing changes before
the staging repo is promoted to release repo, which leaves master temporary
broken. Is there any reason why promoting can't happen first? Like that
commit triggers Travis CI?
Karel
On Wed, 05 Jun 2013 14:00:24 -0300
Bruno Oliveira <bruno(a)abstractj.org> wrote:
Hi Karel, we follow this process
https://github.com/aerogear/collateral/blob/master/RELEASE_HOWTO.md
And we're open for suggestions, feel free to change it.
Daniel Passos wrote:
> On Wed, Jun 5, 2013 at 10:51 AM, Karel Piwko <kpiwko(a)redhat.com
> <mailto:kpiwko@redhat.com>> wrote:
>
> I think it would be great if repositories that require it, like [1] [2]
> are bumped in master after it goes off staging. That would solve
> some confusion
> about readme instructions not being accurate.
>
>
> My bad, won't happen again
>
> Karel
>
> [1]
https://github.com/aerogear/aerogear-android-todo
> [2]
https://github.com/aerogear/aerogear-android-integration-tests
>
> On Tue, 04 Jun 2013 11:31:26 -0300
> Bruno Oliveira <bruno(a)abstractj.org <mailto:bruno@abstractj.org>>
wrote:
>
> > Good morning guys.
> >
> > Passos will release AeroGear Android 1.0.1, but before press THE
> button
> > to release. Would be nice if some bug hunters could test it and file
> > bugs to Passos.
> >
> > Staging repository:
> >
> >
>
https://repository.jboss.org/nexus/content/repositories/jboss_releases_st...
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/aerogear-dev
_______________________________________________
aerogear-dev mailing list
aerogear-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev