[prev in list] [next in list] [prev in thread] [next in thread] 

List:       jakarta-commons-user
Subject:    Re: Commons Configuration Web Site Broken
From:       Oliver Heger <oliver.heger () oliver-heger ! de>
Date:       2014-03-16 15:33:04
Message-ID: 5325C430.9040708 () oliver-heger ! de
[Download RAW message or body]

The site has been redeployed. The problems should be fixed now.

Oliver

Am 14.03.2014 21:35, schrieb Oliver Heger:
> Am 14.03.2014 02:35, schrieb Martin Gainty:
>>
>>   
>>
>>
>>> Date: Thu, 13 Mar 2014 14:33:04 +0000
>>> Subject: Re: Commons Configuration Web Site Broken
>>> From: sebbaz@gmail.com
>>> To: user@commons.apache.org
>>>
>>> On 12 March 2014 20:27, Oliver Heger <oliver.heger@oliver-heger.de> wrote:
>>>> Hit Matt,
>>>>
>>>> thanks for spotting this. It looks like an intermediate snapshot version
>>>> of the site has been deployed while experimenting with the new look & feel.
>>>>
>>>> Situation is worse because the latest 1.10 release has been made from a
>>>> special branch while the site in trunk still is based on the 1.9 version.
>>
>>>>
>>>> @Site experts: What is the best option to fix this? I think the approach
>>>> suggested once by sebb would make sense: Create a branch from the 1.10
>>>> release tag, do some modifications (mainly switch to most recent commons
>>>> parent) and deploy from there?
>> MG>roll 2.x out to a special branch 
>> MG>(dont allow  trunk to have for more than one experimental branch)
>> MG>merge the 1.10 back to trunk
>> MG>then cut the 1.10 release candidate
>> MG>run your tests including smoke and loadrunner
>> MG>then vote on 1.10 being pushed to distros
>> MG>release the 1.10
>>
>> MG>diff the 2.0 branch and resolve all insane deltas
>> MG>repeat the process enumerated above..
> 
> Thanks, Martin!
> 
> However, Configuration 1.10 has already been released. This was done
> from a branch created from trunk; then some features and fixes from
> trunk were ported to this branch making the content of the 1.10 release.
> 
> So trunk indeed contains the most recent development version; however,
> the most recent site is on the 1.10 release branch.
> 
> Oliver
> 
>>
>>>> WDYT?
>>>
>>> That the site issue should be discussed in a new mail thread on the
>>> dev list please.
>>>
>>>> Oliver
>>>>
>>>> Am 12.03.2014 05:36, schrieb Matt Hughes:
>>>>> Hi, I'm trying to use commons configuration, but the web site is broken in
>>>>> a couple of ways. It references 2.0-SNAPSHOT, and the latest stable version
>>>>> it lists is 1.9.
>>>>>
>>>>> It doesn't appear to be possible to get to the JavaDoc for 1.9 or 1.10 at
>>>>> all.
>>>>>
>>>>> The download page and version history page refer to 1.9, but the latest
>>>>> release is 1.10, so all of the 1.9 download links are broken.
>>>>>
>>>>> It would be helpful for new users of commons configuration to be able to
>>>>> access javadoc and download the latest stable release through the web site
>>>>> without having to hunt around for the "archives..." link at the bottom of
>>>>> the download page or change the URL to find the 1.10 version.
>>>>>
>>>>> Thanks,
>>>>> mch
>>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: user-unsubscribe@commons.apache.org
>>>> For additional commands, e-mail: user-help@commons.apache.org
>>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: user-unsubscribe@commons.apache.org
>>> For additional commands, e-mail: user-help@commons.apache.org
>>>
>>  		 	   		  
>>
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@commons.apache.org
> For additional commands, e-mail: user-help@commons.apache.org
> 


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

[prev in list] [next in list] [prev in thread] [next in thread]