So my initial assumption was occrect and I won't add this issue to changes.xml.
thanks! Am 11.06.2013 um 17:32 schrieb Paul Benedict <pbened...@apache.org>: > I always thought changes.xml was to describe the release package. If the > ticket produced no artifact update, why does it need to be part of the > distribution? > > > On Tue, Jun 11, 2013 at 10:30 AM, Gary Gregory <garydgreg...@gmail.com>wrote: > >> I see no harm as adding it to changes.xml, it's a doc change that we might >> as well document like any other doc or site change. >> >> Gary >> >> >> On Tue, Jun 11, 2013 at 10:08 AM, Benedikt Ritter <brit...@apache.org >>> wrote: >> >>> Hello, >>> >>> we had this request [1] to create a git mirror for [beanutils]. I >> created a >>> [infra] ticket and linked it to our ticket. Now infra has created the >>> mirror and closed their issue. My question is: do I track that beanutils >>> now has a git mittor via changes.xml? >>> >>> It is an information that users may be interested in. But usually >>> changes.xml just contains changes to the code and we do have the jira >>> report. So I've probably given the answer myself? >>> >>> TIA, >>> Benedikt >>> >>> [1] https://issues.apache.org/jira/browse/BEANUTILS-404 >>> >>> >>> -- >>> 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
