commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Simone Tripodi <simonetrip...@apache.org>
Subject Re: [pool] Site update
Date Mon, 04 Apr 2011 15:23:52 GMT
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://people.apache.org/~simonetripodi/
http://www.99soft.org/



On Mon, Apr 4, 2011 at 5:14 PM, Phil Steitz <phil.steitz@gmail.com> wrote:
> 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 not
> as messy as I thought.  Here are some things we need to get sorted
> to get a reasonable site build working from trunk.
>
> 0) temporarily disable clirr, as there is no earlier version of the
> artifact to compare against
> 1) fix many javadoc and checkstyle warnings
> 2) post-1.5.6 release cleanup - update changes.xml, release notes,
> doap, javadoc nav link
>
> I will take care of 2) if you don't beat me to it.  Item 1) is not
> strictly necessary, but getting things a little better would be good
> before publishing the javadoc on the site.
>
> We should probably also add some text on the main page explaining
> the plan for 2.0.
>
> Phil
>> Simo
>>
>> http://people.apache.org/~simonetripodi/
>> http://www.99soft.org/
>>
>>
>>
>> On Mon, Apr 4, 2011 at 4:08 PM, Phil Steitz <phil.steitz@gmail.com> wrote:
>>> On 4/4/11 4:25 AM, sebb wrote:
>>>> On 4 April 2011 07:36, Phil Steitz <phil.steitz@gmail.com> 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 publish based on
>>>>> the updated 1_5_X branch.  Once we get the 2.0 sources consolidated
>>>>> and site build repaired, we can publish an updated version.  The
>>>>> site now being replicated has correct download page, javadoc links,
>>>>> and reports corresponding to the 1.5.6 release.
>>>> I thought that is what people did anyway - generate the site from the tag?
>>>>
>>> I usually update trunk and generate the public site from trunk, so
>>> it reflects current development.  The tag won't work in general,
>>> because any post-release updates - most importantly the version
>>> number - won't be reflected in the tag.  In any case, the [pool]
>>> site now reflects the 1.5.x branch.  Once we get our 2.0 house in a
>>> little better order, I think the site should be updated to reflect
>>> the new stuff.
>>>
>>> Phil
>>>>> Phil
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>>>>> For additional commands, e-mail: dev-help@commons.apache.org
>>>>>
>>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>>>> For additional commands, e-mail: dev-help@commons.apache.org
>>>>
>>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>>> For additional commands, e-mail: dev-help@commons.apache.org
>>>
>>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>> For additional commands, e-mail: dev-help@commons.apache.org
>>
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org


Mime
View raw message