A couple of small things before release: 1) are the NOTICE files sufficient? 2) Is everyone ready for me to push the button to create the tag? :)
Once the release:perform task has been completed, I think it is safe to begin committing patches and outstanding code toward 0.2. As we discussed before, if the release is voted down, 0.1 will never make it to the public distribution and we will address any of the issues for 0.2. -Matt On 6/23/11 1:18 PM, "Franklin, Matthew B." <[email protected]> wrote: >On 6/23/11 12:47 PM, "Marlon Pierce" <[email protected]> wrote: > >>-----BEGIN PGP SIGNED MESSAGE----- >>Hash: SHA1 >> >>How close are we to having the 0.1-INCUBATING release complete? There >>are a lot of patches and other commits that are on hold. Should we make >>a branch? > >IMHO, No. I have been tied up all week, but just broke free and I should >be able to get the artifacts out for vote this week. > >One question for Ate, or someone else familiar with the process. It was >mentioned that we could push the button on the master and project releases >at the same time, but if the rave-project depends on the released master, >how would this work? > >-Matt > >> >> >>Marlon >>-----BEGIN PGP SIGNATURE----- >>Version: GnuPG/MacGPG2 v2.0.16 (Darwin) >>Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ >> >>iQEcBAEBAgAGBQJOA24jAAoJEEfVXEODPFIDbS0H/Rh/4QrTO6GedMmVDOzsxChG >>qOS8/OjAoqGT3afP+ixtOrlNuZ8f91SrlSDbnNEa09gskgO6SrI+A9PmzRCvRt/6 >>iePErogIADyd3krs8zl89VtcRQODT5dgWruKAYA+VZsgj9mjP4bBt0ZRDYCsUoGx >>pcpb/HnjyEHWz9JHz7jIh6vwgtsKIlnUmmtve2yJcgu3GD3dsCHcDd3lCPi3EAlf >>BmlUzXcuCNRCq/Rrgni+xkDnh24pgRrmxqv/eykBlkXQqjm48Uio3WWpGkzmOn/O >>7uJDqlKSb847pnteWG1lAlBVwkFoBltCqeqpEX4rhULhjqgSA747tvFSg5q1uyk= >>=MFK1 >>-----END PGP SIGNATURE----- > >
