The question is more what our policy is. In my opinion you need one of two policies:
* snapshots are deployed manually * snapshots are deployed automatically from a specific branch We have used manual as our policy. If we change that’s fine, but we should stop manual deployment and clarify the deployment frequency so that people can set their update policy in their settings.xml appropriately. A vote would be required imho... and a discuss beforehand. On Thu 10 Jan 2019 at 06:18, Enrico Olivelli <eolive...@gmail.com> wrote: > We should only have to setup a CI job which does > mvn deploy > > AFAIK ASF Jenkins are allowed to push snapshots > > Enrico > > Il gio 10 gen 2019, 00:34 Mickael Istria <mist...@redhat.com> ha scritto: > > > On Wednesday, January 9, 2019, Robert Scholte <rfscho...@apache.org> > > wrote: > > > > > I've just deployed the SNAPSHOTs from current master to > > > repository.apache.org > > > > > > > Thanks a lot! Could it be done continuously? Technicallu, a CI > job.checking > > the repo could tale care of doing it soon after each change without > further > > human effort. > > > > > > -- > > Mickael Istria > > Eclipse IDE <https://www.eclipse.org/downloads/eclipse-packages/> > > developer, for Red Hat Developers <https://developers.redhat.com/> > > > -- > > > -- Enrico Olivelli > -- Sent from my phone
