Sounds like a plan. :) I will let you know how the release process goes on my side later today.
And big +1 for Claus suggestions regarding the automated releases. pon., 18.05.2015 o 10:07 użytkownik Andrea Cosentino <ancosen1...@yahoo.com.invalid> napisał: > You're right.Maybe we can propose a different release process to ASF. > Anyway, for the next release (after 2.14.3) I can do the RM to allow > rotation between us. > Andrea Cosentino---------------------------------- > Apache Camel Committer > Email: ancosen1...@yahoo.com > Twitter: @oscerd2 > Github: oscerd > > > On Monday, May 18, 2015 9:53 AM, Claus Ibsen <claus.ib...@gmail.com> > wrote: > > > On Mon, May 18, 2015 at 9:29 AM, Henryk Konsek <hekon...@gmail.com> > wrote: > > I can give it a try. I feel bad about not helping you with the releases > ;) . > > > > I will start the release setup/process today late evening (EMEA time). > > > > Yay thanks. > > I wonder if ASF has on the table or we can reuse the CI servers to do > the release. It seems a bit silly that releases has to be done on > peoples computers, instead of build servers. > > Do anyone know if other ASF projects do releases using either the > existing CI servers at ASF, or external servers? > > Doing releases for hawtio / fabric8 and others is just a matter of > clicking a run button on jenkins, and then promote the release from > the mvn staged repo to central when its approved. > > I wonder if we could get into that direction for ASF Camel also so > more people and its much easier to do releases, so we can cut releases > faster and more frequent. > > Frankly I would like to see build servers do "candidate builds" on a > regular schedule, so doing a release is a matter of just promoting one > of those as the RC, which then allow us to do more time boxed and > scheduled releases. > > This allows us to deliver fixes to users quicker and also they would > not have to wait 2-4 months for a fix etc. > > Okay that is another talk. But I think its worth down the road. Its > 2015 and not 2008 - Camel need to step up as well. > > > > Cheers! > > > > pon., 18.05.2015 o 05:07 użytkownik Willem Jiang <willem.ji...@gmail.com > > > > napisał: > > > >> Yeah, I think it could be good if we have more than one release manager > :) > >> > >> All you need to do is have a signed release key, clean build box with > good > >> internet connection and this doc[1]. Before the release, you may need > to > >> run some test to verify the kit is ready :) > >> > >> [1]https://camel.apache.org/release-guide.html > >> > >> -- > >> Willem Jiang > >> > >> Red Hat, Inc. > >> Web: http://www.redhat.com > >> Blog: http://willemjiang.blogspot.com (English) > >> http://jnn.iteye.com (Chinese) > >> Twitter: willemjiang > >> Weibo: 姜宁willem > >> > >> > >> > >> On May 17, 2015 at 6:10:00 PM, Christian Müller ( > >> christian.muel...@gmail.com) wrote: > >> > +1 > >> > > >> > Maybe a new committer want to be the RM? > >> > > >> > Best, > >> > Christian > >> > Am 11.05.2015 17:51 schrieb "Claus Ibsen" : > >> > > >> > > Hi > >> > > > >> > > I think we should if possible later this month release a new patch > >> > > release of this branch. > >> > > > >> > > Any thoughts? > >> > > > >> > > -- > >> > > Claus Ibsen > >> > > ----------------- > >> > > Red Hat, Inc. > >> > > Email: cib...@redhat.com > >> > > Twitter: davsclaus > >> > > Blog: http://davsclaus.com > >> > > Author of Camel in Action: http://www.manning.com/ibsen > >> > > hawtio: http://hawt.io/ > >> > > fabric8: http://fabric8.io/ > >> > > > >> > > >> > >> > > > > -- > Claus Ibsen > ----------------- > Red Hat, Inc. > Email: cib...@redhat.com > Twitter: davsclaus > Blog: http://davsclaus.com > Author of Camel in Action: http://www.manning.com/ibsen > hawtio: http://hawt.io/ > fabric8 <http://hawt.io/fabric8>: http://fabric8.io/ > >
