[aerogear-dev] AeroGear Android 1.0.1 - Under staging repository

[Bruno Oliveira]

Hi Karel, feel free to send a PR on it. Looks like our release process 
is ok and must be improved.

For 2, do you think is possible to stage it and make the CI test all 
projects which depends on it?

Just an example:

- Staging aerogear-controller
- In some place that I truly don't know update with the repo staged
- CI Build aerogear-controller demo and TODO to check if something was 
broken

Wdyt?

Karel Piwko wrote:
> On Thu, 06 Jun 2013 12:04:20 -0300
> Bruno Oliveira<bruno at abstractj.org>  wrote:
>
>> We wrote that a long long time ago. Would be really nice to hear your
>> thoughts.
>>
>> We do not promote first, we stage it first. In this way people can test
>> with the staging repository, if some bug are found we still have time to
>> revert it.
>
> This makes perfect sense. I'm proposing following scheme
>
> 1/ locally update a component
> 2/ stage
> 3/ locally update all that depend/help testing on 1/ (examples, tests with
> different lifecycle, etc.)
> 4/ test, if failed return to 1/
> 5/ promote (move staged to JBoss Nexus/Maven Central)
> 6/ push 1/ and every 3/ into aerogear repos
>
> The only difference w.r.t current scheme iirc, would be that 6/ is always done
> at last, not right after 1/ and 3/.
>
> Pros is that git repositories can be build all the time, cons
> is that developers/testers need to update 3/ by themselves. Depends on how many
> manual testing is about to be done, not a problem with automation in place :-)
>
>> As far is I know if you promote it, it would be released on Maven Central.
>>
>> Karel Piwko wrote:
>>> 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 at abstkpiwko@redhat.comractj.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 at redhat.com
>>>>> <mailto:kpiwko at 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 agakpiwko at redhat.comin
>>>>>
>>>>>       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 at abstractj.org<mailto:bruno at abstractj.org>>
>>>>> wrote:
>>>>>
>>>>>        >   Good morning guys.
>>>>>        >
>>>>>        >   Passos will release AeroGear Android 1.0.1, but before press THE
>>>>>       button
>>>>>        >   to release. Woukpiwko at redhat.comld 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_staging_profile-097/
>>>>>
>>>>> _______________________________________________
>>>>> aerogear-dev mailing list
>>>>> aerogear-dev at lists.jboss.org
>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>> _______________________________________________
>>>> aerogear-dev mailing list
>>>> aerogear-dev at lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>> _______________________________________________
>>> aerogear-dev mailing list
>>> aerogear-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev

-- 
-
abstractj