I think I understand what Gary means. I once wrote down the process to release Apache Portals Application for other PMC members here: - http://wiki.apache.org/portals/Applications/Release_Process I guess the process is almost the same in other projects (log4j2 or possibly lang).
There are many time consuming / error-prone steps like Gary mentioned. I have no idea on how we can possibly improve the process though. Regards, Woonsan ----- Original Message ----- > From: Gary Gregory <garydgreg...@gmail.com> > To: Commons Developers List <dev@commons.apache.org> > Cc: > Sent: Tuesday, October 8, 2013 2:10 PM > Subject: Re: [DISCUSS] Why is releasing such a pain and what can we do to > make it easier? > > Luckily, Ralph handles release manager duties, for which I am > grateful. So I cannot speak to the ease or difficulty of the process > there. > > Gary > > On Oct 8, 2013, at 14:08, Benedikt Ritter <benerit...@gmail.com> wrote: > >> Hey Gary, >> >> you are involved in other projects (like log4j2) how do they do it? Is it > easier to release log4j2 than it is to release for example [lang]? >> >> Benedikt >> >> Send from my mobile device >> >>> Am 08.10.2013 um 19:52 schrieb Gary Gregory > <garydgreg...@gmail.com>: >>> >>> IMO the problems are dealing with Nexus, a web site, and a > 'dist' >>> directory; that THREE things to get just right, none are 100% > automated. >>> With Nexus you have to do some manual steps. If you look at all the >>> instructions for any commons component, it is long, a combo of manual > and >>> Maven+Nexus magic and error prone. It is not fun and a barrier. >>> >>> Gary >>> >>> >>>> On Tue, Oct 8, 2013 at 12:46 PM, Benedikt Ritter > <brit...@apache.org> wrote: >>>> >>>> Hi, >>>> >>>> one of the points that seem to always come up once in a while is > the >>>> process of releasing components. I've never done it myself so > I'm asking >>>> people who have done it: >>>> >>>> What are the problems and how can we make releasing easier? >>>> Is the complexity of the parent pom a problem? (Do we really need > all the >>>> stuff that is declared there?) >>>> Is there a way to automate all the stuff that needs to be done in a >>>> portable way? >>>> Would it be possible to automate release for example on a Jenkins > instance? >>>> >>>> Benedikt >>>> >>>> >>>> -- >>>> http://people.apache.org/~britter/ >>>> http://www.systemoutprintln.de/ >>>> http://twitter.com/BenediktRitter >>>> http://github.com/britter >>> >>> >>> >>> -- >>> E-Mail: garydgreg...@gmail.com | ggreg...@apache.org >>> Java Persistence with Hibernate, Second > Edition<http://www.manning.com/bauer3/> >>> JUnit in Action, Second Edition > <http://www.manning.com/tahchiev/> >>> Spring Batch in Action <http://www.manning.com/templier/> >>> Blog: http://garygregory.wordpress.com >>> Home: http://garygregory.com/ >>> Tweet! http://twitter.com/GaryGregory >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org >> For additional commands, e-mail: dev-h...@commons.apache.org > >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
