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

Great news! I've started testing the Android Pipes. Is there any list with the changes performed in version 1.0.1? On Tue, 2013-06-04 at 11:31 -0300, Bruno Oliveira 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 <mailto:aerogear-dev@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

On Tue, Jun 4, 2013 at 12:31 PM, Apostolos Emmanouilidis <aemmanou(a)redhat.com&gt; wrote: Great news! I've started testing the Android Pipes. Is there any list with the changes performed in version 1.0.1? Can you see it on roadmap[1], on Issue tracker[2] or on git commits[3] [1] http://aerogear.org/docs/planning/roadmaps/AeroGearAndroid/ [2] https://issues.jboss.org/issues/?jql=project%20%3D%20AGDROID%20AND %20fixVersion%20%3D%20%221.0.1%22 [3] https://github.com/aerogear/aerogear-android/compare/78b63293...8fe1bdda On Tue, 2013-06-04 at 11:31 -0300, Bruno Oliveira 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

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.

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&gt; 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...

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

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&lt;bruno(a)abstractj.org&gt; 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&lt;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@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 _______________________________________________ aerogear-dev mailing list aerogear-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/aerogear-dev

-1 at first glance, it looks very confuse to me

On Jun 6, 2013, at 7:41 PM, Tadeas Kriz <tkriz(a)redhat.com&gt; wrote: > How about making a different ("staging") branch for the aerogear-android-todo repository, which will be using the 1.0.1 version. And after the 1.0.1 is promoted into public repository, merge the "staging" branch back into master. That wouldn't confuse newcomers, because when they'd clone master, it would fetch aerogear from Maven Central. And for the "staging" branch, there should probably be information about the staging nexus repository in the Readme file. > > ----- Original Message ----- > From: "Bruno Oliveira" <bruno(a)abstractj.org&gt; > To: "AeroGear Developer Mailing List" <aerogear-dev(a)lists.jboss.org&gt; > Sent: Thursday, June 6, 2013 5:04:20 PM > Subject: Re: [aerogear-dev] AeroGear Android 1.0.1 - Under staging repository > > 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. > > 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&lt;bruno(a)abstractj.org&gt; 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&lt;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@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... >>>> >>>> ____________________________________________

On Thu, 06 Jun 2013 12:04:20 -0300 Bruno Oliveira&lt;bruno(a)abstractj.org&gt; 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&lt;bruno@abstkpiwko(a)redhat.comractj.org&gt; 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&lt;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 agakpiwko(a)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@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. Woukpiwko(a)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_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 >> _______________________________________________ >> 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