Kai, Basically, it takes all of sinan's nice release handling stuff and moves it into a stand alone tool.
You can find the official sources here (master branch is what is released, next branch is what will be released next) https://github.com/erlware/relcool The absolute latest and greatest can be found in my repo. https://github.com/ericbmerritt/relcool Development is on going so expect API changes and the like. That said its stable and being used in production right now. There is also a rebar plugin for it. Eric On Jan 4, 2013, at 1:42 PM, Kai Janson <[email protected]> wrote: > Hi guys, > > Maybe I have skipped over it, but is there a link to the tool? > If it has sinan functionality and enhanced features I'd like to give it a > shot. > > Thank you! > --Kai > > On Monday, October 15, 2012 11:10:24 AM UTC-5, Eric Merritt wrote: > My biggest need right now is other people giving it a shot to work it out in > unexpected ways. Granted thats got to wait until I get some documentation (I > will do that today btw). > > On Oct 15, 2012, at 10:12 AM, Jordan Wilberding <[email protected]> wrote: > >> I agree as well. If you need some help, just let me know. >> >> On Thu, Oct 11, 2012 at 6:09 AM, Martin Logan <[email protected]> wrote: >> I agree. How long until Relcool is in beta condition? It would be nice to >> have a somewhat production grade alternative for people at the time of >> deprecating Sinan >> >> >> On Wed, Oct 10, 2012 at 9:52 AM, Eric Merrit <[email protected]> wrote: >> Guys, >> >> Now that relcool is in a semi usable state I would like to kick of the >> deprecation of Sinan. Its going to be a somewhat long slow process, but its >> something that I think needs to happen. >> >> * Two things I need to do before getting this started is to write up a >> migration pattern for folks. >> * The second thing is that relcool needs some bundling support. >> >> Once these are done Sinan should be deprecated. However, I think its >> probably useful to start warning people about that upcoming fact. >> >> Eric >> >> -- >> You received this message because you are subscribed to the Google Groups >> "erlware-dev" group. >> To post to this group, send email to [email protected]. >> To unsubscribe from this group, send email to >> [email protected]. >> For more options, visit this group at >> http://groups.google.com/group/erlware-dev?hl=en. >> >> >> >> >> -- >> Martin Logan >> Erlang & OTP in Action (Manning) http://manning.com/logan >> http://twitter.com/martinjlogan >> http://erlware.org >> >> >> -- >> You received this message because you are subscribed to the Google Groups >> "erlware-dev" group. >> To post to this group, send email to [email protected]. >> To unsubscribe from this group, send email to >> [email protected]. >> For more options, visit this group at >> http://groups.google.com/group/erlware-dev?hl=en. >> >> >> -- >> You received this message because you are subscribed to the Google Groups >> "erlware-dev" group. >> To post to this group, send email to [email protected]. >> To unsubscribe from this group, send email to >> [email protected]. >> For more options, visit this group at >> http://groups.google.com/group/erlware-dev?hl=en. > > > -- > You received this message because you are subscribed to the Google Groups > "erlware-dev" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/erlware-dev/-/nbE3GFx7lTUJ. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/erlware-dev?hl=en. -- You received this message because you are subscribed to the Google Groups "erlware-dev" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/erlware-dev?hl=en.
