On Tue, Jul 29, 2008 at 11:05 AM, Niall Pemberton <[EMAIL PROTECTED]> wrote: > On Tue, Jul 29, 2008 at 3:47 PM, Matt Benson <[EMAIL PROTECTED]> wrote: >> >> --- Rahul Akolkar <[EMAIL PROTECTED]> wrote: >> >>> On Mon, Jul 28, 2008 at 6:54 PM, Matt Benson >>> <[EMAIL PROTECTED]> wrote: >>> > Is a `mvn site` from a src distribution supposed >>> to >>> > generate download_[component].cgi? >>> <snip/> >>> >>> No. >>> >>> >>> > If not, are we >>> > intended to make sure we preserve the existing >>> file or >>> > re-create it when deploying the site? >>> <snap/> >>> >>> Don't need to do anything special for it (its >>> preserved by default). >>> >>> Process: >>> * Update <commons.release.version> in pom >>> * "mvn commons:download-page" to gen the .xml >>> download page >>> * "mvn site-deploy" (or similar) >>> >>> As an aside (though perhaps its related), I saw a >>> couple of updates to >>> SVN tags go by -- it'd be best if we can avoid >>> these. >>> >> >> As these were updates directly related to creating >> RC5, I have no idea how to appease you in this regard. >> :( > > Theres really two ways of doing this. > > 1) Do all the updates in the trunk and then tag > 2) Create a branch for the release, update there and then tag > > IMO best to choose 1) if the whole focus is only on the current > release and 2) if other people are want to continue to do development > and not have to hold off on commits while the release is being done. > <snip/>
Yup, thanks, my thoughts as well. -Rahul > Niall > >> -Matt >> >>> -Rahul >>> >>> >>> > This is >>> > confusing to me. >>> > >>> > Thanks, >>> > Matt >>> > >>> > >>> --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
