On 2 June 2016 at 23:15, Gary Gregory wrote:
> On Thu, Jun 2, 2016 at 2:57 PM, Benedikt Ritter wrote:
>
>> Emmanuel Bourg schrieb am Do., 2. Juni 2016 um
>> 23:39 Uhr:
>>
>> > Hi all,
>> >
>> > A part of the release process is to update the web site. I wonder if
>> > this could be simplified wit
> > A part of the release process is to update the web site. I wonder if
> > this could be simplified with a Jenkins job watching for the release
> > tags and building/uploading the new site automatically. That would
> > make one less thing to think about when releasing new versions. I
> > suspect
One big pain is releasing IMO is having to manage BOTH Nexus (with the
extra checksum mess) AND SVN dist/dev + dist/release.
It would be nice if Nexus had a menu option as part of Closing a repo to
"remove extra checksum"...
Gary
On Thu, Jun 2, 2016 at 2:39 PM, Emmanuel Bourg wrote:
> Hi all,
On Thu, Jun 2, 2016 at 2:57 PM, Benedikt Ritter wrote:
> Emmanuel Bourg schrieb am Do., 2. Juni 2016 um
> 23:39 Uhr:
>
> > Hi all,
> >
> > A part of the release process is to update the web site. I wonder if
> > this could be simplified with a Jenkins job watching for the release
> > tags and bu
Emmanuel Bourg schrieb am Do., 2. Juni 2016 um
23:39 Uhr:
> Hi all,
>
> A part of the release process is to update the web site. I wonder if
> this could be simplified with a Jenkins job watching for the release
> tags and building/uploading the new site automatically. That would make
> one less
Hi all,
A part of the release process is to update the web site. I wonder if
this could be simplified with a Jenkins job watching for the release
tags and building/uploading the new site automatically. That would make
one less thing to think about when releasing new versions. I suspect the
most di
