Hi Hasan, all, I wanted to ask infrya, but then new proposals came into the discussion and it was no longer clear what we wanted.
I think we should ask infra if they could provide gitlab or something similar. I don't think that it is an option to have every individaul repo created by infra. If it's not possible to have a solution run by infra we can: - Look for an external solution like github or bitbucket, the legal implications of this would have to be clarified. The legal issue I see is ensuring that only apache committer (with signed ICLA) effectively push code. - Enhance the tool so we can work with our process even when just having a single repository Cheers, Reto On Wed, Sep 3, 2014 at 7:42 AM, Hasan Hasan <[email protected]> wrote: > Hi Reto, all > > Have you clarified how we are going to implement that? > Are we going to ask INFRA for each repository or do we consider to store > the code outside of ASF infrastructure? github, gitlab, or ? > Any legal and financial consequences? > > Cheers > Hasan > > > On Mon, Sep 1, 2014 at 3:18 PM, Reto Gmür <[email protected]> wrote: > > > 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 > > > > >> > > > > >> > > > > > > > > > > > > > > >
