[aerogear-dev] Non-Java release processes

[Lucas Holmquist]

On Jul 23, 2014, at 11:46 AM, Matthias Wessendorf <matzew at apache.org> wrote:

> 
> 
> 
> On Wed, Jul 23, 2014 at 5:40 PM, Lucas Holmquist <lholmqui at redhat.com> wrote:
> 
> On Jul 23, 2014, at 11:22 AM, Matthias Wessendorf <matzew at apache.org> wrote:
> 
>> Thanks for all the feedback !
>> 
>> I have added the Cordova and iOS processes to our wiki - linking to those from its landing page:
>> https://github.com/aerogear/collateral/wiki
>> 
>> 
>> Regarding plain JavaScrip, is this gist correct:
>> https://gist.github.com/matzew/14f93693c8362b753782
> 
> well, not sure about "JavaScrip",  but that is pretty much what i do for the “JavaScript” stuff.  i currently don’t sign the release, but do "git tag -a ‘x.y.z’ -m’x.y.z’”
> 
> while i create a branch for the new pending release,  i also like to create a tag for it.  so x.y.z-beta  or something like that.
> 
> 
> cool! I am sure the JavaScrip folks are OK w/ that too :) 
> 
> Can you fork and update the gist, as needed ? 
> 
sure

> 
> @branches: I do that, on UPS, as needed, out of the tag - I guess that's what you do too, right ? 
yea,  

>  
> 
> 
>> 
>> if so, I will add a JS section - others, a JS centric fork of that document is more than welcome
>> 
>> -M
>> 
>> 
>> On Tue, Jul 8, 2014 at 10:31 AM, Corinne Krych <corinnekrych at gmail.com> wrote:
>> 
>> On 08 Jul 2014, at 10:29, Christos Vasilakis <cvasilak at gmail.com> wrote:
>> 
>> >>
>> >> On Jul 8, 2014, at 11:17 AM, Corinne Krych <corinnekrych at gmail.com> wrote:
>> >>
>> >>
>> >> On 08 Jul 2014, at 10:12, Christos Vasilakis <cvasilak at gmail.com> wrote:
>> >>
>> >>>>
>> >>>> On Jul 8, 2014, at 10:07 AM, Matthias Wessendorf <matzew at apache.org> wrote:
>> >>>>
>> >>>> Hi,
>> >>>>
>> >>>> at the face2face we had a discussion about formalizing our release processes for non-java project.
>> >>>> The Java guide is, IMO, still relevant and up-to-date:
>> >>>> https://github.com/aerogear/collateral/wiki/Release-Process-(Java)
>> >>>>
>> >>>>
>> >>>> For the non-java projects I started a few gists
>> >>>>
>> >>>> * for Cordova and JavaScript, I think this could be used:
>> >>>> https://gist.github.com/matzew/14f93693c8362b753782
>> >>>>
>> >>>> Note: I am not sure if some extra steps are missing for things like npm oe bower
>> >>>>
>> >>>> * for iOS, I think we can formalize on something like this:
>> >>>> https://gist.github.com/matzew/941883df5bd0abcf1d61
>> >>>
>> >>> looks good +1
>> >>> did some changes here [1]  and modified the ‘Perform’ section adding cocoapods new approach to spec publish and the step to update the spec itself.
>> >>>
>> >>> If we are fine with it, will go ahead and add it on our 'https://github.com/aerogear/collateral/wiki'
>> >>>
>> >>
>> >>
>> >> don’t we miss:
>> >> - step 0: ‘send PR to cocoa pod’
>> >
>> > this step was replaced from cocoa pods with the 'pod trunk push’ command, no need to send PR on their repo any more. That was my update on matzew gist :)
>> 
>> 
>> Ahhhh!
>> Good to clarify with a doc actually :)
>> 
>> >
>> >
>> >> - step 5: update all demo Podfile with relevant tag
>> >
>> > +1, have updated my gist[1] with this step too
>> >
>> > Thanks,
>> > Christos
>> >
>> >
>> >
>> >
>> >>
>> >>> Thanks
>> >>> Christos
>> >>>
>> >>> [1] https://gist.github.com/cvasilak/114c7280b627ae6bcd9f
>> >>>
>> >>> [
>> >>>>
>> >>>>
>> >>>> Greetings,
>> >>>> Matthias
>> >>>>
>> >>>>
>> >>>> --
>> >>>> Matthias Wessendorf
>> >>>>
>> >>>> blog: http://matthiaswessendorf.wordpress.com/
>> >>>> sessions: http://www.slideshare.net/mwessendorf
>> >>>> twitter: http://twitter.com/mwessendorf
>> >>>> _______________________________________________
>> >>>> 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
>> 
>> 
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at 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
>> _______________________________________________
>> 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
> 
> 
> 
> -- 
> Matthias Wessendorf 
> 
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140723/caf141cd/attachment.html