[aerogear-dev] Github releases

classic Classic list List threaded Threaded
9 messages Options
Reply | Threaded
Open this post in threaded view
|

[aerogear-dev] Github releases

Luke Holmquist
Hi all,

yup,  sending this on a Friday, at 3pm EST.

while going over some of the JS push tutorial docs, i found that the links to the AG JS lib were point to somewhat older releases.  While we could try to remember to update these docs after every release,  i propose we use githubs really neat “release”  button.

Basically, we would still tag our releases normally,  and after we push those up,  we can press the “Draft a New Release” button.  

This allows us to choose an existing tag, but some release notes in, and also mark as a pre-release

but the best part,  is that we can now link to the “latest” release in our docs






wdyt?


-Luke

_______________________________________________
aerogear-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/aerogear-dev
Reply | Threaded
Open this post in threaded view
|

Re: [aerogear-dev] Github releases

Bruno Oliveira
+1

abstractj
PGP: 0x84DC9914


On Fri, Jul 25, 2014 at 4:13 PM, Lucas Holmquist <[hidden email]> wrote:

Hi all,


yup,  sending this on a Friday, at 3pm EST.

while going over some of the JS push tutorial docs, i found that the links to the AG JS lib were point to somewhat older releases.  While we could try to remember to update these docs after every release,  i propose we use githubs really neat “release”  button.

Basically, we would still tag our releases normally,  and after we push those up,  we can press the “Draft a New Release” button.  

This allows us to choose an existing tag, but some release notes in, and also mark as a pre-release

but the best part,  is that we can now link to the “latest” release in our docs






wdyt?


-Luke


_______________________________________________
aerogear-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/aerogear-dev
Reply | Threaded
Open this post in threaded view
|

Re: [aerogear-dev] Github releases

danielbevenius
+1 Sounds good


On 25 July 2014 21:59, Bruno Oliveira <[hidden email]> wrote:
+1

abstractj
PGP: 0x84DC9914


On Fri, Jul 25, 2014 at 4:13 PM, Lucas Holmquist <[hidden email]> wrote:

Hi all,


yup,  sending this on a Friday, at 3pm EST.

while going over some of the JS push tutorial docs, i found that the links to the AG JS lib were point to somewhat older releases.  While we could try to remember to update these docs after every release,  i propose we use githubs really neat “release”  button.

Basically, we would still tag our releases normally,  and after we push those up,  we can press the “Draft a New Release” button.  

This allows us to choose an existing tag, but some release notes in, and also mark as a pre-release

but the best part,  is that we can now link to the “latest” release in our docs






wdyt?


-Luke


_______________________________________________
aerogear-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/aerogear-dev


_______________________________________________
aerogear-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/aerogear-dev
Reply | Threaded
Open this post in threaded view
|

Re: [aerogear-dev] Github releases

Corinne Krych
That is neat indeed
++
Corinne
On 26 Jul 2014, at 06:23, Daniel Bevenius <[hidden email]> wrote:

> +1 Sounds good
>
>
> On 25 July 2014 21:59, Bruno Oliveira <[hidden email]> wrote:
> +1
> —
> abstractj
> PGP: 0x84DC9914
>
>
> On Fri, Jul 25, 2014 at 4:13 PM, Lucas Holmquist <[hidden email]> wrote:
>
> Hi all,
>
>
> yup,  sending this on a Friday, at 3pm EST.
>
> while going over some of the JS push tutorial docs, i found that the links to the AG JS lib were point to somewhat older releases.  While we could try to remember to update these docs after every release,  i propose we use githubs really neat “release”  button.
>
> Basically, we would still tag our releases normally,  and after we push those up,  we can press the “Draft a New Release” button.  
>
> This allows us to choose an existing tag, but some release notes in, and also mark as a pre-release
>
> but the best part,  is that we can now link to the “latest” release in our docs
>
> This is the link created: https://github.com/aerogear/aerogear-js-dist/releases/latest
>
>
> this will link to: https://github.com/aerogear/aerogear-js/releases/tag/1.5.1
>
>
>
> wdyt?
>
>
> -Luke
>
>
> _______________________________________________
> aerogear-dev mailing list
> [hidden email]
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
> _______________________________________________
> aerogear-dev mailing list
> [hidden email]
> https://lists.jboss.org/mailman/listinfo/aerogear-dev


_______________________________________________
aerogear-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/aerogear-dev
Reply | Threaded
Open this post in threaded view
|

Re: [aerogear-dev] Github releases

cvasilak
In reply to this post by danielbevenius
+9001 helpful indeed

-
Christos

On 26 Ιουλ 2014, at 7:23 π.μ., Daniel Bevenius <[hidden email]> wrote:

+1 Sounds good


On 25 July 2014 21:59, Bruno Oliveira <[hidden email]> wrote:
+1

abstractj
PGP: 0x84DC9914


On Fri, Jul 25, 2014 at 4:13 PM, Lucas Holmquist <[hidden email]> wrote:

Hi all,


yup,  sending this on a Friday, at 3pm EST.

while going over some of the JS push tutorial docs, i found that the links to the AG JS lib were point to somewhat older releases.  While we could try to remember to update these docs after every release,  i propose we use githubs really neat “release”  button.

Basically, we would still tag our releases normally,  and after we push those up,  we can press the “Draft a New Release” button.  

This allows us to choose an existing tag, but some release notes in, and also mark as a pre-release

but the best part,  is that we can now link to the “latest” release in our docs






wdyt?


-Luke


_______________________________________________
aerogear-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/aerogear-dev

_______________________________________________
aerogear-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/aerogear-dev

_______________________________________________
aerogear-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/aerogear-dev
Reply | Threaded
Open this post in threaded view
|

Re: [aerogear-dev] Github releases

Matthias Wessendorf
In reply to this post by Luke Holmquist
Yeah, I saw that too, it's nice a feature they have 


+1 on using that (versus specific tags/versions)

-Matthias


On Fri, Jul 25, 2014 at 9:13 PM, Lucas Holmquist <[hidden email]> wrote:
Hi all,

yup,  sending this on a Friday, at 3pm EST.

while going over some of the JS push tutorial docs, i found that the links to the AG JS lib were point to somewhat older releases.  While we could try to remember to update these docs after every release,  i propose we use githubs really neat “release”  button.

Basically, we would still tag our releases normally,  and after we push those up,  we can press the “Draft a New Release” button.  

This allows us to choose an existing tag, but some release notes in, and also mark as a pre-release

but the best part,  is that we can now link to the “latest” release in our docs






wdyt?


-Luke

_______________________________________________
aerogear-dev mailing list
[hidden email]
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

_______________________________________________
aerogear-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/aerogear-dev
Reply | Threaded
Open this post in threaded view
|

Re: [aerogear-dev] Github releases

Daniel Passos-2
+1


On Sat, Jul 26, 2014 at 5:50 AM, Matthias Wessendorf <[hidden email]> wrote:
Yeah, I saw that too, it's nice a feature they have 


+1 on using that (versus specific tags/versions)

-Matthias


On Fri, Jul 25, 2014 at 9:13 PM, Lucas Holmquist <[hidden email]> wrote:
Hi all,

yup,  sending this on a Friday, at 3pm EST.

while going over some of the JS push tutorial docs, i found that the links to the AG JS lib were point to somewhat older releases.  While we could try to remember to update these docs after every release,  i propose we use githubs really neat “release”  button.

Basically, we would still tag our releases normally,  and after we push those up,  we can press the “Draft a New Release” button.  

This allows us to choose an existing tag, but some release notes in, and also mark as a pre-release

but the best part,  is that we can now link to the “latest” release in our docs






wdyt?


-Luke

_______________________________________________
aerogear-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/aerogear-dev
qmx
Reply | Threaded
Open this post in threaded view
|

Re: [aerogear-dev] Github releases

qmx
Administrator
In reply to this post by Luke Holmquist
+3.14159

--
qmx
_______________________________________________
aerogear-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/aerogear-dev
Reply | Threaded
Open this post in threaded view
|

Re: [aerogear-dev] Github releases

Lukas Fryc
In reply to this post by Luke Holmquist


On Fri, Jul 25, 2014 at 9:13 PM, Lucas Holmquist <[hidden email]> wrote:
Hi all,

yup,  sending this on a Friday, at 3pm EST.

while going over some of the JS push tutorial docs, i found that the links to the AG JS lib were point to somewhat older releases.  While we could try to remember to update these docs after every release,  i propose we use githubs really neat “release”  button.

Basically, we would still tag our releases normally,  and after we push those up,  we can press the “Draft a New Release” button.  

This allows us to choose an existing tag, but some release notes in, and also mark as a pre-release

but the best part,  is that we can now link to the “latest” release in our docs






wdyt?


-Luke

_______________________________________________
aerogear-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/aerogear-dev


_______________________________________________
aerogear-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/aerogear-dev