I strongly suggest that you do not attempt to create a binary release at this time. (Binary releases physically include your dependencies, so licensing is much more complicated.)
Get the source release right first. On Fri, Dec 4, 2015 at 4:29 PM, Edward Zhang <yonzhang2...@gmail.com> wrote: > In this case, we want to cut a release branch/tag from master branch, and > based on the release branch/tag, we create tarball for source and binary, > so community can consistently download the same bits and we can also have a > document to describe what we have in this release. Please suggest > > Thanks > Edward > > On Fri, Dec 4, 2015 at 2:48 PM, Henry Saputra <henry.sapu...@gmail.com> > wrote: > >> How is it master is not stable enough? Master should be stable and >> contains code that should pass all tests. >> >> Could you elaborate more about proposed dev cycle? >> >> - Henry >> >> >> On Fri, Dec 4, 2015 at 11:49 AM, Dendukuri, Hemanth <hdenduk...@ebay.com> >> wrote: >> > Hello Eagle Dev, >> > >> > I noticed that Master branch is not >> stable enough for End2End functional testing. >> > I see a need to create a new tag to test >> and release the new stable eagle version, with the changes that went into >> it , since our last release. >> > Reply if anyone need time to merge their >> new feature or have any other questions regarding this effort. >> > >> > Regards >> > Hemanth >> > >>
