Branches and 1.0.0.Final tag (was: Re: UnifiedPush Server: Code-Freeze - and UPS.next)
by Matthias Wessendorf
Hi team,
the 1.0.0.Final has been tagged for testing - will share the staging repo
soon.
Besides that, we now have a 1.0.x branch ([1]), used for the 1.0.x release
series - as discussed in [2].
As mentioned earlier, the master version has been set to "1.1.0-SNAPSHOT"
and will contain new features (e.g. WindowsPush) and backports of fixes
from the 1.0.x branch.
Greetings,
Matthias
[1] https://github.com/aerogear/aerogear-unifiedpush-server/tree/1.0.x
[2] http://staging.aerogear.org/docs/planning/roadmaps/UnifiedPush
On Thu, Aug 21, 2014 at 7:49 AM, Christos Vasilakis <cvasilak(a)gmail.com>
wrote:
> +1 to include RC1, sounds good
>
>
> -
> Christos
>
>
> On Aug 21, 2014, at 8:26 AM, Daniel Bevenius <daniel.bevenius(a)gmail.com>
> wrote:
>
> +1 Sounds good to me getting RC1 in.
>
>
> On 20 August 2014 23:12, Bruno Oliveira <bruno(a)abstractj.org> wrote:
>
>> +1 on get RC1 in.
>>
>> On 2014-08-20, Matthias Wessendorf wrote:
>> > Hello,
>> >
>> > I will tag tomorrow morning.
>> > This PR will get in as well
>> > https://github.com/aerogear/aerogear-unifiedpush-server/pull/364
>> >
>> > This gives us a few days (Thurs, Friday, Monday, Tuesday, and perhaps
>> > Wednesday next week) to test the TAG.
>> > So we can have the release to Maven Central by next Wednesday/Thursday.
>> >
>> > Oh, one more thing:
>> > ATM Bill Burk is already doing the rc-1 release, followed by a rc-2 next
>> > week:
>> > http://lists.jboss.org/pipermail/keycloak-dev/2014-August/002460.html
>> >
>> > If there are no concerns, I'd like to get that rc-1 in as well. It
>> fixes a
>> > few minor bugs on our "UI":
>> > * https://issues.jboss.org/browse/AGPUSH-950 -> Luke found it
>> > * logout sessions from KC admin, works not 100% w/ beta4. noticed
>> tonight.
>> > Tested w/ rc-1 -> works there.
>> >
>> >
>> > Any thoughts?
>> >
>> > Thanks!
>> > Matthias
>> >
>> >
>> >
>> > On Mon, Aug 18, 2014 at 3:11 PM, Matthias Wessendorf <matzew(a)apache.org
>> >
>> > wrote:
>> >
>> > > Hello,
>> > >
>> > > as mentioned in [1] we should have a code-freeze period of a few days
>> > > before we do the final release.
>> > > Release for UPS.1.0.0.Final date will be August 26th.
>> > >
>> > > I'd like to do the code-freeze tomorrow(Tuesday, 19th) evening. I'd
>> like
>> > > to create a 1.0.0.Final tag (or a branch) and only
>> > > 'blocker' or 'critical' fixes should be allowed to be merged during
>> that
>> > > time (to that particular branch/tag).
>> > > Basic goal: minimize risks!
>> > >
>> > > (The JIRA tickets for the umbrella "Mobile Push 1.0" are almost all
>> around
>> > > Quickstarts and our docs, see [2])
>> > >
>> > >
>> > > Once the 1.0.0.Final is released, I'd like to create a 1.0.x branch
>> for
>> > > follow-up releases, as needed (see [3]).
>> > > The version number on the "1.0.x" branch will start with
>> 1.0.1-SNAPSHOT
>> > > On MASTER branch, I'd like to set the version to 1.1.0-SNAPSHOT.
>> > >
>> > > Fixes done on the 1.0.x branch will be merged/cherry-picked MASTER
>> branch
>> > > as well.
>> > >
>> > >
>> > > Moving forward to our next 1.1.0 UPS release, on MASTER, we will be
>> > > working on new features, like:
>> > > * More analytics
>> > > * More mobile network (Windows, Kindle, etc)
>> > > * JavaEE7 updates (focus on WildFly / Undertow, ConcurrencyUtils, etc)
>> > > * Alternative Datastores (like Mongo) ?
>> > >
>> > >
>> > > Any thoughts ?
>> > > -Matthias
>> > >
>> > >
>> > > [1]
>> http://lists.jboss.org/pipermail/aerogear-dev/2014-August/008810.html
>> > > [2]
>> > >
>> https://issues.jboss.org/browse/AGPUSH/fixforversion/12323754/?selectedTa...
>> > > [3] http://aerogear.org/docs/planning/roadmaps/UnifiedPush/
>> > >
>> > >
>> > > --
>> > > Matthias Wessendorf
>> > >
>> > > blog: http://matthiaswessendorf.wordpress.com/
>> > > sessions: http://www.slideshare.net/mwessendorf
>> > > twitter: http://twitter.com/mwessendorf
>> > >
>> >
>> >
>> >
>> > --
>> > Matthias Wessendorf
>> >
>> > blog: http://matthiaswessendorf.wordpress.com/
>> > sessions: http://www.slideshare.net/mwessendorf
>> > twitter: http://twitter.com/mwessendorf
>>
>> > _______________________________________________
>> > aerogear-dev mailing list
>> > aerogear-dev(a)lists.jboss.org
>> > https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>>
>> --
>>
>> abstractj
>> PGP: 0x84DC9914
>> _______________________________________________
>> 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
>
--
Matthias Wessendorf
blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
8 years, 7 months
UnifiedPush Server: Code-Freeze - and UPS.next
by Matthias Wessendorf
Hello,
as mentioned in [1] we should have a code-freeze period of a few days
before we do the final release.
Release for UPS.1.0.0.Final date will be August 26th.
I'd like to do the code-freeze tomorrow(Tuesday, 19th) evening. I'd like to
create a 1.0.0.Final tag (or a branch) and only
'blocker' or 'critical' fixes should be allowed to be merged during that
time (to that particular branch/tag).
Basic goal: minimize risks!
(The JIRA tickets for the umbrella "Mobile Push 1.0" are almost all around
Quickstarts and our docs, see [2])
Once the 1.0.0.Final is released, I'd like to create a 1.0.x branch for
follow-up releases, as needed (see [3]).
The version number on the "1.0.x" branch will start with 1.0.1-SNAPSHOT
On MASTER branch, I'd like to set the version to 1.1.0-SNAPSHOT.
Fixes done on the 1.0.x branch will be merged/cherry-picked MASTER branch
as well.
Moving forward to our next 1.1.0 UPS release, on MASTER, we will be working
on new features, like:
* More analytics
* More mobile network (Windows, Kindle, etc)
* JavaEE7 updates (focus on WildFly / Undertow, ConcurrencyUtils, etc)
* Alternative Datastores (like Mongo) ?
Any thoughts ?
-Matthias
[1] http://lists.jboss.org/pipermail/aerogear-dev/2014-August/008810.html
[2]
https://issues.jboss.org/browse/AGPUSH/fixforversion/12323754/?selectedTa...
[3] http://aerogear.org/docs/planning/roadmaps/UnifiedPush/
--
Matthias Wessendorf
blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
8 years, 7 months
