oxide team mailing list archive

[Chris Coulson <chris.coulson@xxxxxxxxxxxxx>]

On 29/07/14 18:23, Chris Coulson wrote:
> Hi,
>
> This sounds fine. I've added some comments inline just to clarify a
> couple of points.
>
> On 29/07/14 17:16, David Barth wrote:
>> Hi,
>>
>> Here is the release plan we discussed today during our call.
>>
>> Aug. 5th - 1.2 preview release, with cookie manager & script injection
>> support.
>>
> This would basically be a snapshot from trunk.
>
>> Aug. 18th - target date for a oxide-1.2 release
> This is the estimated branch date, rather than the release date (the
> release date would be ~6 weeks after). This is the point at which 1.2
> becomes the "next" Oxide release, as the 1.1 branch currently is (with
> 1.0 branch being the current "stable" branch).

Sorry, I should have pointed out - this doesn't actually affect anything
in the original proposal :)

> I've made the release cycle diagram public to illustrate this -
> https://docs.google.com/a/canonical.com/presentation/d/1cJ_2nhHgv1A4tMUy4-7Tc1kt5r861a0CnYaG9GiOqIo/
>
> Regards
> - Chris
>
>> This gives us about 2 weeks to test the preview release integrated
>> with the rest of the RTM components, before we can make a 1.2 release.
>>
>> Comments? Thoughts?
>>
>> David
>>
>

Attachment: signature.asc
Description: OpenPGP digital signature