+1 Reto Gmür schreef op 1-9-2014 15:18: > Ok, so my proposal: > > We should have a git repository per maven project and version each project > individually. We should release very often. It shall be possible to call > for a vote on releasing multiple artifacts, but also in this case there are > different source for each tarballs. > > Cheers, > Reto > > > On Fri, Aug 29, 2014 at 7:32 AM, Hasan Hasan <[email protected]> wrote: > >> Hi Reto, all >> >> On Thu, Aug 28, 2014 at 3:39 PM, Reto Gmür <[email protected]> wrote: >> >>> Hi all, >>> >>> We really should get to an agreement on how to handle this. >>> >>> Should we collect concrete proposals and then have a vote? >>> >> It looks like this is the better way to go. >> >> Cheers >> Hasan >> >>> Cheers, >>> Reto >>> >>> >>> On Wed, Aug 27, 2014 at 2:40 PM, Reto Gmür <[email protected]> wrote: >>> >>>> The maven publishing guidelines is here: >>>> http://www.apache.org/dev/publishing-maven-artifacts.html >>>> >>>> I don't know about any apache project where the releases are built by a >>>> build-server. >>>> >>>> Cheers, >>>> Reto >>>> >>>> >>>> On Tue, Aug 26, 2014 at 10:24 PM, Andy Seaborne <[email protected]> >> wrote: >>>>> On 26/08/14 19:51, Minto van der Sluis wrote: >>>>> >>>>>> Reto Gmür schreef op 26-8-2014 11:35: >>>>>> >>>>>>> It should be >>>>>>> >>>>>>> mvn release:prepare >>>>>>> mvn release:deploy >>>>>>> >>>>>>> Go to: https://repository.apache.org/ and close the release, call >> for >>>>>>> vote >>>>>>> and if it succeded promote the release. >>>>>>> >>>>>>> Upload the source release and its signature to >>>>>>> https://dist.apache.org/repos/dist/, update website >>>>>>> >>>>>>> The release is not built by the build server but locally. >>>>>>> >>>>>>> This in my opinion is a major no-no. Developers should not manually >>>>>> build releases. Doing this manually is not only error prone, but >> local >>>>>> configuration might also pollute the released artefacts. Possibly >>>>>> leading to a situation which is not reproducible. This is a lesson I >>>>>> learned the hard way. >>>>>> >>>>>> How do other Apache projects produce their releases? >>>>>> >>>>>> >>>>> The Jena build is local. >>>>> >>>>> https://cwiki.apache.org/confluence/display/JENA/Release+Process >>>>> >>>>> so the build is slightly different to the develop builds because it >> uses >>>>> different targets and adds a -P >>>>> >>>>> e.g. >>>>> mvn release:prepare -Papache-release >>>>> mvn release:deploy -Papache-release >>>>> >>>>> The Apache release profile comes from the general Apache parent and >>>>> produces the source-release file for putting in www.apache.org/dist. >>>>> >>>>> Andy >>>>> >>>>>
-- ir. ing. Minto van der Sluis Software innovator / renovator Xup BV Mobiel: +31 (0) 626 014541
