_
From: Rob Tompkins
To: Bruno P. Kinoshita
Cc: Commons Developers List
Sent: Tuesday, 30 October 2018 1:33 AM
Subject: Re: [site] update release process (Was: Re: [VOTE] Release Commons
Imaging 1.0-alpha1 based on RC1)
> On Oct 29, 2018, at 7:24 AM, Rob Tompkins wrote:
>
tely empty.
Feel free to ping me on slack if anything arises. I do know that we’re 14 hours
different in terms of timezones though.
Cheers,
-Rob
>
> -Rob
>
>>
>>
>>
>> Thanks heaps
>> Bruno
>>
>>
>>
>>
>> _
gt; Cc: Bruno P. Kinoshita
> Sent: Monday, 29 October 2018 2:49 AM
> Subject: [site] update release process (Was: Re: [VOTE] Release Commons
> Imaging 1.0-alpha1 based on RC1)
>
>
>
> This is mildly on me for not updating the release docs recently. I’ll put
> that o
Cc: Bruno P. Kinoshita
Sent: Monday, 29 October 2018 2:49 AM
Subject: [site] update release process (Was: Re: [VOTE] Release Commons Imaging
1.0-alpha1 based on RC1)
This is mildly on me for not updating the release docs recently. I’ll put that
on my docket for the week.
PS. @Bruno solid
This is mildly on me for not updating the release docs recently. I’ll put that
on my docket for the week.
PS. @Bruno solid work and many thanks for rolling the RC.
Cheers,
-Rob
> On Oct 28, 2018, at 9:35 AM, Gary Gregory wrote:
>
> Hello Bruno,
>
> Thank you for preparing the RC.
>
> MD5 a
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
2014/1/21 Gary Gregory
> On Mon, Dec 23, 2013 at 4:23 PM, Benedikt Ritter
> wrote:
>
> > Hi,
> >
> > I've forked your repo, Thomas and tried the skin out. Looks like you've
> > fixed the problems with clear. Can we integrate your work into SVN?
> >
>
> Any news here?
>
As I said, I could not re
On Mon, Dec 23, 2013 at 4:23 PM, Benedikt Ritter wrote:
> Hi,
>
> I've forked your repo, Thomas and tried the skin out. Looks like you've
> fixed the problems with clear. Can we integrate your work into SVN?
>
Any news here?
Gary
>
> Regards,
> Benedikt
>
>
> 2013/11/10 Benedikt Ritter
>
> >
Hi,
I've forked your repo, Thomas and tried the skin out. Looks like you've
fixed the problems with clear. Can we integrate your work into SVN?
Regards,
Benedikt
2013/11/10 Benedikt Ritter
> Nice to see this moving forward. What is next? Can we integrate the
> changes you made in github into
Nice to see this moving forward. What is next? Can we integrate the changes you
made in github into svn?
Benedikt
Send from my mobile device
> Am 10.11.2013 um 19:14 schrieb Thomas Neidhart :
>
>> On 11/09/2013 08:35 PM, Christian Grobmeier wrote:
>> I like it pretty much. Good job.
>
> There
On 11/09/2013 08:35 PM, Christian Grobmeier wrote:
> I like it pretty much. Good job.
There are still a few minor issues with the pretty printing of source
code and the output of the clirr report.
> Anything which can go back into fluido and gives us the chnace to work
> with the "original fluido
I like it pretty much. Good job.
Anything which can go back into fluido and gives us the chnace to work
with the "original fluido"?
On 2 Nov 2013, at 18:47, Thomas Neidhart wrote:
Hi all,
I have further reworked the skin available at
https://github.com/netomi/commons-skin-fluido and the res
Hi all,
I have further reworked the skin available at
https://github.com/netomi/commons-skin-fluido and the results can be
seen here:
http://people.apache.org/~tn/commons/fluido/commons/
http://people.apache.org/~tn/commons/fluido/codec/
http://people.apache.org/~tn/commons/fluido/lang3/
The ski
On 14 January 2013 10:51, Mladen Turk wrote:
> On 01/14/2013 11:36 AM, Thomas Neidhart wrote:
>>
>> On Mon, Jan 14, 2013 at 11:27 AM, Mladen Turk wrote:
>>
>>> Hi,
>>>
>>> Had to generate a new key file cause after 10 years my old one expired ;)
>>> I updated KEYS file in svn but don't know how t
On 01/14/2013 11:36 AM, Thomas Neidhart wrote:
On Mon, Jan 14, 2013 at 11:27 AM, Mladen Turk wrote:
Hi,
Had to generate a new key file cause after 10 years my old one expired ;)
I updated KEYS file in svn but don't know how to publish that to a site.
Anyone willing to push that file online?
On Mon, Jan 14, 2013 at 11:27 AM, Mladen Turk wrote:
> Hi,
>
> Had to generate a new key file cause after 10 years my old one expired ;)
> I updated KEYS file in svn but don't know how to publish that to a site.
>
> Anyone willing to push that file online?
>
Hi Mladen,
this should do the trick:
Hi,
Had to generate a new key file cause after 10 years my old one expired ;)
I updated KEYS file in svn but don't know how to publish that to a site.
Anyone willing to push that file online?
Regards
--
^TM
-
To unsubscribe,
On 05/04/2011 20:05, Simone Tripodi wrote:
> Hi Phil,
> sorry if I'm late on it due to the [discovery] (I'd like to put an end
> at least to one thing I touch :P) but I would suggest following the
> Mark Thomas' suggestion:
>
> - move the current /trunk on a branch, something like POOL_2_FEATURE;
Hi Phil,
sorry if I'm late on it due to the [discovery] (I'd like to put an end
at least to one thing I touch :P) but I would suggest following the
Mark Thomas' suggestion:
- move the current /trunk on a branch, something like POOL_2_FEATURE;
- move the current POOL_1_X to /trunk;
- push the si
Hi Phil!
I'm at work now, but this evening at home I'll be able start taking
care of 0) and 1)!
Just for the record: time ago, in the commons-pool wiki page, I
reported some points we already discussed in the ML, I hope they can
help you for designing the roadmap.
Have a nice day!
Simo
http://pe
On 4/4/11 7:19 AM, Simone Tripodi wrote:
> Hi Phil,
> I think I can be helpful there, but I din't understand which steps are
> needed to get the trunk in a better order, I would be glad to fix it!
> Thanks in advance! :)
Thanks, Simo!
After cleaning up my local checkout, I see now that things are
Hi Phil,
I think I can be helpful there, but I din't understand which steps are
needed to get the trunk in a better order, I would be glad to fix it!
Thanks in advance! :)
Simo
http://people.apache.org/~simonetripodi/
http://www.99soft.org/
On Mon, Apr 4, 2011 at 4:08 PM, Phil Steitz wrote:
>
On 4/4/11 4:25 AM, sebb wrote:
> On 4 April 2011 07:36, Phil Steitz wrote:
>> I will be sending the 1.5.6 release announcement shortly. When
>> updating the pool website, I started by trying to use trunk, but
>> found the output confusing, since we are in process of changing the
>> groupId and pa
On 4 April 2011 07:36, Phil Steitz wrote:
> I will be sending the 1.5.6 release announcement shortly. When
> updating the pool website, I started by trying to use trunk, but
> found the output confusing, since we are in process of changing the
> groupId and package name. I decided, therefore, to
I will be sending the 1.5.6 release announcement shortly. When
updating the pool website, I started by trying to use trunk, but
found the output confusing, since we are in process of changing the
groupId and package name. I decided, therefore, to publish based on
the updated 1_5_X branch. Once w
You're right! Sorry for the noise!
Jochen
On Wed, Aug 4, 2010 at 12:25 PM, Phil Steitz wrote:
> Jochen Wiedmann wrote:
>> Thanks, Phil!
>>
>
> We missed the fact that the files are not world-readable. Sorry, my
> bad. They need to be readable by apbackup. You (jochen) need to
> either u+r or
Jochen Wiedmann wrote:
> Thanks, Phil!
>
We missed the fact that the files are not world-readable. Sorry, my
bad. They need to be readable by apbackup. You (jochen) need to
either u+r or run fixPerms to make the files world readable.
Phil
>
> On Tue, Aug 3, 2010 at 12:31 PM, Phil Steitz wrot
Thanks, Phil!
On Tue, Aug 3, 2010 at 12:31 PM, Phil Steitz wrote:
> Jochen Wiedmann wrote:
>> Ping?
>>
> Files look fine to me. Just opened
> https://issues.apache.org/jira/browse/INFRA-2909
>
> Phil
>>
>> On Mon, Aug 2, 2010 at 11:40 AM, Jochen Wiedmann
>> wrote:
>>> Sent to the wrong commons,
Jochen Wiedmann wrote:
> Ping?
>
Files look fine to me. Just opened
https://issues.apache.org/jira/browse/INFRA-2909
Phil
>
> On Mon, Aug 2, 2010 at 11:40 AM, Jochen Wiedmann
> wrote:
>> Sent to the wrong commons, now querying the right one ...
>>
>>
>> On Fri, Jul 30, 2010 at 3:49 PM, Jochen W
Ping?
On Mon, Aug 2, 2010 at 11:40 AM, Jochen Wiedmann
wrote:
> Sent to the wrong commons, now querying the right one ...
>
>
> On Fri, Jul 30, 2010 at 3:49 PM, Jochen Wiedmann
> wrote:
>> Hi,
>>
>> I have updated /www/commons.apache.org/fileupload almost 8 hours ago,
>> but http://commons.apac
Sent to the wrong commons, now querying the right one ...
On Fri, Jul 30, 2010 at 3:49 PM, Jochen Wiedmann
wrote:
> Hi,
>
> I have updated /www/commons.apache.org/fileupload almost 8 hours ago,
> but http://commons.apache.org/fileupload is still showing the old
> page. Am I missing something?
>
Replaced
http://commons.apache.org/build/commons.ent
with the newest version. Hopefully, this resolves the issue. Need to
wait until the change makes it to the web server as it seems.
Oliver
2007/8/19, simon <[EMAIL PROTECTED]>:
> On Sun, 2007-08-19 at 00:45 +0200, Oliver Zeigermann wrote:
> >
On Sun, 2007-08-19 at 00:45 +0200, Oliver Zeigermann wrote:
> Folks!
>
> I have finally managed to make some progress on my "navigation still
> points to jakarta" problem and it seems to be it is broken in all
> components.
Hmm, yes this appears to be true. I published the logging module
recently
Folks!
I have finally managed to make some progress on my "navigation still
points to jakarta" problem and it seems to be it is broken in all
components.
That is really strange as all subcomponent trunks have this DTD
http://commons.apache.org/build/maven-build.dtd'>
Which - among other things
Hey Dennis!
Thanks for helping :)
However, I still have this problem. Any other idea? Cleaning maven
caches and stuff did not help either. I noticed the build also
succeeds when there is no ../commons-build.
Any other location to define where commons.ent comes from?
Thanks in advance
Oliver
The included entity &commons; is fetched from ../commons-build/... in
our Maven 1 setup. So you probably need to do "svn update" on that
directory to get the latest TLP changes.
Zeigermann, Oliver wrote:
Folks!
I just can't seem to properly update the transaction site. My problem
is that the
Folks!
I just can't seem to properly update the transaction site. My problem
is that the common links (included by "&commons;" in navigation.xml)
keep on pointing to Jakarta. I jsut can't find the location where I
would have to change that.
Any hint highly appreciated.
Thanks in advance
Oliver
42 matches
Mail list logo
