Hello. > > Le 19/03/2012 01:01, Christian Grobmeier a écrit : > > On Mon, Mar 19, 2012 at 12:25 AM, Gilles Sadowski > > <gil...@harfang.homelinux.org> wrote: > >>> Not to forget the grandfather of release guides: > >>> http://commons.apache.org/releases/release.html > >> > >> I've just had a brief look at that one; I did not know it existed... > > > > not very well linked imho... if it is linked > > > >> Is it maintained and up-to-date? > > > > Same situation like UsingNexus: the guys who use it, should update it.
Then it is as I said: Useless. The "guys who use it" are the newbies who by definition do not know what needs to be updated. They will try to follow the instructions, see that some do not work, post to the ML, wait for answers, try to figure the cause of the problems, and finally write a new document that contains things that worked for them. > > Sometimes it happens. :-) Yes, but even when it happens it is not always to the benefit of the newbies. One example: "UsingNexus" contains two ways to create a branch. Thinking that I should lean on the "modern" side I first tried the "maven way". It did not work (at least not when literally following the description). Then, I was told (by Sebb on the ML) to take the "manual way"... > > So perhaps rather than creating a third document, these recent notes > should replace the existing pages and get linked to everything else. > Otherwise we would end up with 3 documents and another release manager > candidate would stumble upon an old one, then create a fourth document, > then be pointed to this one and say he didn't know it existed, then put > this fourth document on-line, then ... This will indeed happen but I think even if new notes are posted to the web site or the wiki. Not all "Commons" components have the same configuration and what seems to work for one does not necessarily work for another. [My notes work for "Commons Math" (at least, I can ensure that it worked for releasing v3.0).] I've just uploaded them on the Wiki: http://wiki.apache.org/commons/GillesSadowski/ReleaseMiniHowto Please, let me know of any important thing which I might have omitted. There are some formatting problems as I meant it to be a basic text file, not a wiki document (and I don't want it to become yet another useless wiki document). Also, IMHO it should not include specifics on using subversion or ssh etc. but only the bare minimum. As such, the old "release.html" on the web site can be useful if it means to contain the "full story" (such as explaining how to setup "no login ssh" or how to create GPG keys). [The probelm is that the longer a document is, the less likely it will be kept in sync with the changing procedures...] I don't think that the mini-howto should stay on the Wiki. Rather, it should be directly accessible in some sub-directory of "trunk" where a release manager newbie is not likely to miss it, and where it can be updated efficiently (e.g. at the same time a change to the "pom" file would require it). Regards, Gilles > [...] --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
