camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Claus Ibsen <claus.ib...@gmail.com>
Subject Re: Camel release process - Separation the manual, maven reports and javadoc etc.
Date Fri, 09 Oct 2009 15:34:52 GMT
On Fri, Oct 9, 2009 at 3:34 PM, Hadrian Zbarcea <hzbarcea@gmail.com> wrote:
> Actually, it's more than that.
>
> The issue with the manual is that it downloads a lot of the wiki locally
> (with imgs and all) to build the pdf.  That's both time and bandwidth
> consuming.
> I would also think that camel-web should move somehow.  Either only building
> it when we activate a profile, or move it to a subproject.  It builds a 30M
> jar, and uploading it during the release process is a lengthy and prone to
> timeouts.  There are other less used components that could move to a
> subproject. Camel grew kinda big lately.
>
> What if we open a wiki page or jira, throw out some ideas and decide
> together on what to do?
>

Yeah good idea with a wiki page. Put it under the developer section
where we got the 2.x designs and ideas for optimizations etc.

Somewhere under this location
http://camel.apache.org/developers.html

> Hadrian
>
>
> On Oct 8, 2009, at 9:45 AM, Jon Anstey wrote:
>
>> On Thu, Oct 8, 2009 at 11:12 AM, Claus Ibsen <claus.ibsen@gmail.com>
>> wrote:
>>
>>> On Thu, Oct 8, 2009 at 3:30 PM, Jon Anstey <janstey@gmail.com> wrote:
>>>>
>>>> On Thu, Oct 8, 2009 at 5:56 AM, Claus Ibsen <claus.ibsen@gmail.com>
>>>
>>> wrote:
>>>>
>>>>> Hi
>>>>>
>>>>> Hadrian and others.
>>>>>
>>>>> The release process for Apache Camel is long and takes much time to do.
>>>>> Can we split out the creating and publication of
>>>>> - manual
>>>>>
>>>>
>>>> Don't we still want to include this in the distribution? If we do, we
>>>
>>> would
>>>>
>>>> need to ensure that it gets generated before or during the release
>>>> process... may be easier to just leave it as is.
>>>>
>>>>
>>>>> - javadoc
>>>>>
>>>>
>>>> This needs to be included with the release no? I think the javadoc jars
>>>
>>> get
>>>>
>>>> published to the maven central repo. Like
>>>>
>>>>
>>>
>>> http://repo2.maven.org/maven2/org/apache/camel/camel-core/2.0.0/camel-core-2.0.0-javadoc.jar
>>>
>>> Ah yeah the -javadoc jars are okay. Its the javadoc link on the camel
>>> website I was referring to.
>>>
>>
>> Ohhhh... in that case then I'm +1 for separating from the release process
>> too.
>>
>>
>>>
>>>
>>>
>>>>
>>>>
>>>>> - maven reports (I doubt even these is updated)
>>>>>
>>>>
>>>> Yeah, last updated time right now is 2009-01-18. So maybe they are
>>>
>>> already
>>>>
>>>> "separate" from the release process :)
>>>>
>>>>
>>>>>
>>>>> I would like to be able to update the javadoc once in a while. So if
>>>>> there was some new maven goal I could run that would be great.
>>>>>
>>>>> The manual generation is error prone. Sometimes the Apache cwiki
>>>>> returns error code 502 etc. I just fixed that in the maven tooling to
>>>>> generate an empty placeholder file.
>>>>> What we could do is to also have a special maven goal that could
>>>>> release and publish the manual.
>>>>>
>>>>> And the maven reports. Either we gotta remove the link to them or have
>>>>> a goal that works and can publish as well.
>>>>>
>>>>> Hadrian what are your thoughts?
>>>>>
>>>>>
>>>>> --
>>>>> Claus Ibsen
>>>>> Apache Camel Committer
>>>>>
>>>>> Open Source Integration: http://fusesource.com
>>>>> Blog: http://davsclaus.blogspot.com/
>>>>> Twitter: http://twitter.com/davsclaus
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Cheers,
>>>> Jon
>>>>
>>>> http://janstey.blogspot.com/
>>>>
>>>
>>>
>>>
>>> --
>>> Claus Ibsen
>>> Apache Camel Committer
>>>
>>> Open Source Integration: http://fusesource.com
>>> Blog: http://davsclaus.blogspot.com/
>>> Twitter: http://twitter.com/davsclaus
>>>
>>
>>
>>
>> --
>> Cheers,
>> Jon
>>
>> http://janstey.blogspot.com/
>
>



-- 
Claus Ibsen
Apache Camel Committer

Open Source Integration: http://fusesource.com
Blog: http://davsclaus.blogspot.com/
Twitter: http://twitter.com/davsclaus

Mime
View raw message