On Jul 2, 2013, at 1:02 PM, Martin Desruisseaux <[email protected]> wrote:
> Le 02/07/13 15:45, Mattmann, Chris A (398J) a écrit : >> I'll grab the 0.3 branch and try to stage a release, and take it >> the rest of the way today! > > Thanks! > > On the "release management" page committed by Suresh [1], I would be curious > to known which step has been applied, and which steps has not been done yet > but could be delayed to the next release. > > Also, do we create a convenience binary file (as a separated download file)? > If so, I can create the binary but what would be the process for releasing it? Hi Martin, Frankly, my head hurts when I try to learn about the binary vs source release rules. Technically speaking what we officially release is the source, but if we are distributing binaries, I always found it easy to apply the same rules (much easier then interpreting the legal guidelines). So only the release manager has to create the binary. Once Chris sets every thing up, from next release you should be able to do it yourself. Its a hard rule that all release artifacts have to be created by the release manager and signed with his key available on the web. From a build perspective, it will be easier if we add the binary creation as a assembly plugin so maven automatically signs the binaries too. We can then just grab all of the signed artifacts and push it into svn dist location. The jars themselves are pushed to nexus repo by the release plugin (inherited from the apache parent plugin) BTW, you do not have to take all the steps on the documents literally, there were just a guidance, you can tune them as it fits the project. Suresh > > Martin > > [2] http://sis.apache.org/release-management.html >
