I already published the site and the reference docs yesterday (mvn
site-deply both on the release tag and the continuum site) but when I
visited the following links, I don't see any changes at all.

http://continuum.apache.org/
http://continuum.apache.org/docs/1.3.5


Can anyone help me with this :)

Thanks,
--
Marica

On Tue, Jan 19, 2010 at 8:02 AM, Marica Tan <[email protected]> wrote:

> The vote has passed with the following results:
>
> +1s  3 binding: Wendy, Brett, Marica
>          1 non-binding: Brent
> No -1s and 0s
>
>
> I'll finalize the release.
>
> Thanks,
> --
> Marica
>
>
>
> On Tue, Jan 19, 2010 at 7:30 AM, Marica Tan <[email protected]> wrote:
>
>> +1 for Beta.
>>
>> - verified signatures and checksums
>> - tried simple build/release both in a distributed and non-distributed
>> build scenarios
>>
>> - Marica
>>
>>
>> On Mon, Jan 18, 2010 at 7:04 PM, Brett Porter <[email protected]> wrote:
>>
>>> +1 for Beta.
>>>
>>> I built the from the source bundle (after checking the signatures). I was
>>> able to run and build a project.
>>>
>>> I still have trouble configuring distributed builds out of the box -
>>> possibly just my misreading the documentation. We need to review this before
>>> a GA and whether we can make it simpler IMO.
>>>
>>> - Brett
>>>
>>> On 13/01/2010, at 6:36 PM, Marica Tan wrote:
>>>
>>> > Hi
>>> >
>>> > The Continuum 1.3.5 release candidate has been staged.
>>> >
>>> > This release includes 23 fixes. You can take a look at the release
>>> notes
>>> > here:
>>> >
>>> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10540&version=15641
>>> >
>>> > While the binaries, including the sources, signatures and checksums,
>>> can be
>>> > downloaded here:
>>> >
>>> http://vmbuild.apache.org/archiva/repository/staged-continuum/org/apache/continuum/continuum-jetty/1.3.5/
>>> >
>>> > <
>>> http://vmbuild.apache.org/archiva/repository/staged-continuum/org/apache/continuum/continuum-jetty/1.3.5/
>>> >
>>> >
>>> http://vmbuild.apache.org/archiva/repository/staged-continuum/org/apache/continuum/continuum-buildagent-jetty/1.3.5/
>>> >
>>> > <
>>> http://vmbuild.apache.org/archiva/repository/staged-continuum/org/apache/continuum/continuum-buildagent-jetty/1.3.5/
>>> >
>>> >
>>> http://vmbuild.apache.org/archiva/repository/staged-continuum/org/apache/continuum/continuum/1.3.5/
>>> >
>>> > <
>>> http://vmbuild.apache.org/archiva/repository/staged-continuum/org/apache/continuum/continuum/1.3.5/
>>> >
>>> >
>>> http://vmbuild.apache.org/archiva/repository/staged-continuum/org/apache/continuum/continuum-buildagent/1.3.5/
>>> >
>>> > Everyone is encouraged to vote and give their feedback.
>>> >
>>> > [ ] +1 Release it! [ ] 0 [ ] -1 Don't release it, because...
>>> >
>>> > The vote will be open for 72 hours.
>>> >
>>> >
>>> > Thanks,
>>> > --
>>> > Marica
>>> >
>>> >
>>> > On Wed, Jan 13, 2010 at 7:48 AM, Marica Tan <[email protected]>
>>> wrote:
>>> >
>>> >> I'll start the release today :-)
>>> >>
>>> >>
>>> >> On Tue, Jan 12, 2010 at 10:47 PM, Wendy Smoak <[email protected]>
>>> wrote:
>>> >>
>>> >>> On Tue, Jan 12, 2010 at 1:24 AM, Emmanuel Venisse
>>> >>> <[email protected]> wrote:
>>> >>>> Is it a GA release? I think it should be.
>>> >>>
>>> >>> I think http://jira.codehaus.org/browse/CONTINUUM-2423 would stop me
>>> >>> from calling it GA.  I reproduced it on trunk.  I didn't try it on
>>> the
>>> >>> branch, but it was reported against 1.3.4 so I assume it's a problem
>>> >>> there too.
>>> >>>
>>> >>> A smooth upgrade path is on my personal list of criteria for a GA
>>> >>> release as well, so I agree with Marica about 2338.
>>> >>>
>>> >>> I don't, however, want to delay 1.3.5 for any of this.  It's already
>>> >>> been four months since 1.3.4.
>>> >>>
>>> >>> Though we don't have a good track record at it, IMO a quick (2-3
>>> >>> weeks?) 1.3.6 with a *limited* number of important fixes would be the
>>> >>> way to go to finally get 1.3.x to GA.
>>> >>>
>>> >>> --
>>> >>> Wendy
>>> >>>
>>> >>
>>> >>
>>>
>>> --
>>> Brett Porter
>>> [email protected]
>>> http://brettporter.wordpress.com/
>>>
>>>
>>>
>>>
>>>
>>
>

Reply via email to