In the cases where the APIs have changed, I'm going to hold off updating the docs until the release gets pushed. That way the docs reflect the current reality. Soon, we hope to have docs checked into the tree, so we can update them as we make changes while at the same time having the branches reflect the reality of the released code.
===
Breaking API Changes:
* In the bookmark module, renamed "childrenIds" to "children". The data in the property is the same: the name was a typo before, it contained whole values, not just ids.
On Thu, Jul 2, 2009 at 4:24 AM, Aaron Boodman <a...@chromium.org> wrote:
> In the cases where the APIs have changed, I'm going to hold off
> updating the docs until the release gets pushed. That way the docs
> reflect the current reality. Soon, we hope to have docs checked into
> the tree, so we can update them as we make changes while at the same
> time having the branches reflect the reality of the released code.
> ===
> Breaking API Changes:
> * In the bookmark module, renamed "childrenIds" to "children". The
> data in the property is the same: the name was a typo before, it
> contained whole values, not just ids.
On Thu, Jul 2, 2009 at 1:24 AM, Aaron Boodman<a...@chromium.org> wrote: > In the cases where the APIs have changed, I'm going to hold off > updating the docs until the release gets pushed. That way the docs > reflect the current reality. Soon, we hope to have docs checked into > the tree, so we can update them as we make changes while at the same > time having the branches reflect the reality of the released code.
> ===
> Breaking API Changes:
> * In the bookmark module, renamed "childrenIds" to "children". The > data in the property is the same: the name was a typo before, it > contained whole values, not just ids.
On Thu, Jul 2, 2009 at 11:02 AM, Aaron Boodman<a...@chromium.org> wrote: > I should have said in the title:
> These are the visible changes for 3.0.191.x, which should start > showing up today or tomorrow.
> - a
> On Thu, Jul 2, 2009 at 1:24 AM, Aaron Boodman<a...@chromium.org> wrote: >> In the cases where the APIs have changed, I'm going to hold off >> updating the docs until the release gets pushed. That way the docs >> reflect the current reality. Soon, we hope to have docs checked into >> the tree, so we can update them as we make changes while at the same >> time having the branches reflect the reality of the released code.
>> ===
>> Breaking API Changes:
>> * In the bookmark module, renamed "childrenIds" to "children". The >> data in the property is the same: the name was a typo before, it >> contained whole values, not just ids.
You should still make an official announcement on
googlechromereleases.blogspot.com because I wouldn't have known if I
didn't venture into this forum today.
On Jul 2, 10:23 pm, Aaron Boodman <a...@chromium.org> wrote:
> Nevermind, the dev release is cancelled this week.
> On Thu, Jul 2, 2009 at 11:02 AM, Aaron Boodman<a...@chromium.org> wrote:
> > I should have said in the title:
> > These are the visible changes for 3.0.191.x, which should start
> > showing up today or tomorrow.
> > - a
> > On Thu, Jul 2, 2009 at 1:24 AM, Aaron Boodman<a...@chromium.org> wrote:
> >> In the cases where the APIs have changed, I'm going to hold off
> >> updating the docs until the release gets pushed. That way the docs
> >> reflect the current reality. Soon, we hope to have docs checked into
> >> the tree, so we can update them as we make changes while at the same
> >> time having the branches reflect the reality of the released code.
> >> ===
> >> Breaking API Changes:
> >> * In the bookmark module, renamed "childrenIds" to "children". The
> >> data in the property is the same: the name was a typo before, it
> >> contained whole values, not just ids.
Is an official announcement about the lack of a weekly Dev release
really that important?
Sure that you would not know *why* there's no Dev release this week,
but having no new entries in googlechromereleases.blogspot.com is
identical to knowing there is no new release as of writing this
message. I don't think anything significant is changed if there is an
official posting that says the reason was it was cancelled this week.
After all, they are weekly Dev releases! Anything can always go wrong/
be found last minute/need extra tweaking/verifying. It already takes
2 days to cut and and then verify each Dev release. Any semi-major
hiccup would easily delay to possibly cancel any week's potential Dev
release.
On Jul 3, 11:45 am, Meok <meok...@gmail.com> wrote:
> You should still make an official announcement on
> googlechromereleases.blogspot.com because I wouldn't have known if I
> didn't venture into this forum today.
> On Jul 2, 10:23 pm, Aaron Boodman <a...@chromium.org> wrote:
> > Nevermind, the dev release is cancelled this week.
> > On Thu, Jul 2, 2009 at 11:02 AM, Aaron Boodman<a...@chromium.org> wrote:
> > > I should have said in the title:
> > > These are the visible changes for 3.0.191.x, which should start
> > > showing up today or tomorrow.
> > > - a
> > > On Thu, Jul 2, 2009 at 1:24 AM, Aaron Boodman<a...@chromium.org> wrote:
> > >> In the cases where the APIs have changed, I'm going to hold off
> > >> updating the docs until the release gets pushed. That way the docs
> > >> reflect the current reality. Soon, we hope to have docs checked into
> > >> the tree, so we can update them as we make changes while at the same
> > >> time having the branches reflect the reality of the released code.
> > >> ===
> > >> Breaking API Changes:
> > >> * In the bookmark module, renamed "childrenIds" to "children". The
> > >> data in the property is the same: the name was a typo before, it
> > >> contained whole values, not just ids.
What I was trying to do with these weekly posts to chromium-extensions
was notify people about upcoming breaking changes to the extensions
system before the changes hit. While we're in development mode, there
will be breaking changes from time to time, and I want to let people
who are experimenting with it know.
I realized a better way to do this would be to send a message here as
soon as a breaking change is checked in. That way, people find out
about it sooner. We can then summarize all the changes (breaking or
otherwise) in the normal release notes.
On Fri, Jul 3, 2009 at 7:26 PM, krtulmay<krtul...@gmail.com> wrote:
> Is an official announcement about the lack of a weekly Dev release
> really that important?
> Sure that you would not know *why* there's no Dev release this week,
> but having no new entries in googlechromereleases.blogspot.com is
> identical to knowing there is no new release as of writing this
> message. I don't think anything significant is changed if there is an
> official posting that says the reason was it was cancelled this week.
> After all, they are weekly Dev releases! Anything can always go wrong/
> be found last minute/need extra tweaking/verifying. It already takes
> 2 days to cut and and then verify each Dev release. Any semi-major
> hiccup would easily delay to possibly cancel any week's potential Dev
> release.
> On Jul 3, 11:45 am, Meok <meok...@gmail.com> wrote:
>> You should still make an official announcement on
>> googlechromereleases.blogspot.com because I wouldn't have known if I
>> didn't venture into this forum today.
>> On Jul 2, 10:23 pm, Aaron Boodman <a...@chromium.org> wrote:
>> > Nevermind, the dev release is cancelled this week.
>> > On Thu, Jul 2, 2009 at 11:02 AM, Aaron Boodman<a...@chromium.org> wrote:
>> > > I should have said in the title:
>> > > These are the visible changes for 3.0.191.x, which should start
>> > > showing up today or tomorrow.
>> > > - a
>> > > On Thu, Jul 2, 2009 at 1:24 AM, Aaron Boodman<a...@chromium.org> wrote:
>> > >> In the cases where the APIs have changed, I'm going to hold off
>> > >> updating the docs until the release gets pushed. That way the docs
>> > >> reflect the current reality. Soon, we hope to have docs checked into
>> > >> the tree, so we can update them as we make changes while at the same
>> > >> time having the branches reflect the reality of the released code.
>> > >> ===
>> > >> Breaking API Changes:
>> > >> * In the bookmark module, renamed "childrenIds" to "children". The
>> > >> data in the property is the same: the name was a typo before, it
>> > >> contained whole values, not just ids.
No problem there, I just thought there was a convention since last
time there was no Dev release an announcement was still made. (That
week, there was a Stable and a Beta update, so they saved the Dev
release for the following week). I figured it was cancelled when I
didn't see anything Thursday but based on what happened last time, I
was still probing the release notes looking for an official "no". It's
all good. I'll know next time.
On Jul 4, 4:18 am, Aaron Boodman <a...@chromium.org> wrote:
> What I was trying to do with these weekly posts to chromium-extensions
> was notify people about upcoming breaking changes to the extensions
> system before the changes hit. While we're in development mode, there
> will be breaking changes from time to time, and I want to let people
> who are experimenting with it know.
> I realized a better way to do this would be to send a message here as
> soon as a breaking change is checked in. That way, people find out
> about it sooner. We can then summarize all the changes (breaking or
> otherwise) in the normal release notes.
> - a
> On Fri, Jul 3, 2009 at 7:26 PM, krtulmay<krtul...@gmail.com> wrote:
> > Is an official announcement about the lack of a weekly Dev release
> > really that important?
> > Sure that you would not know *why* there's no Dev release this week,
> > but having no new entries in googlechromereleases.blogspot.com is
> > identical to knowing there is no new release as of writing this
> > message. I don't think anything significant is changed if there is an
> > official posting that says the reason was it was cancelled this week.
> > After all, they are weekly Dev releases! Anything can always go wrong/
> > be found last minute/need extra tweaking/verifying. It already takes
> > 2 days to cut and and then verify each Dev release. Any semi-major
> > hiccup would easily delay to possibly cancel any week's potential Dev
> > release.
> > On Jul 3, 11:45 am, Meok <meok...@gmail.com> wrote:
> >> You should still make an official announcement on
> >> googlechromereleases.blogspot.com because I wouldn't have known if I
> >> didn't venture into this forum today.
> >> > Nevermind, the dev release is cancelled this week.
> >> > On Thu, Jul 2, 2009 at 11:02 AM, Aaron Boodman<a...@chromium.org> wrote:
> >> > > I should have said in the title:
> >> > > These are the visible changes for 3.0.191.x, which should start
> >> > > showing up today or tomorrow.
> >> > > - a
> >> > > On Thu, Jul 2, 2009 at 1:24 AM, Aaron Boodman<a...@chromium.org> wrote:
> >> > >> In the cases where the APIs have changed, I'm going to hold off
> >> > >> updating the docs until the release gets pushed. That way the docs
> >> > >> reflect the current reality. Soon, we hope to have docs checked into
> >> > >> the tree, so we can update them as we make changes while at the same
> >> > >> time having the branches reflect the reality of the released code.
> >> > >> ===
> >> > >> Breaking API Changes:
> >> > >> * In the bookmark module, renamed "childrenIds" to "children". The
> >> > >> data in the property is the same: the name was a typo before, it
> >> > >> contained whole values, not just ids.
Looks like 3.0.191.3 was just pushed out, I just started getting errors in my bookmark code a few minutes ago. :) Changing childrenIds to children got everything happy again.
Aaron Boodman wrote:
> I should have said in the title:
> These are the visible changes for 3.0.191.x, which should start
> showing up today or tomorrow.
> - a
> On Thu, Jul 2, 2009 at 1:24 AM, Aaron Boodman<a...@chromium.org> wrote:
>> In the cases where the APIs have changed, I'm going to hold off
>> updating the docs until the release gets pushed. That way the docs
>> reflect the current reality. Soon, we hope to have docs checked into
>> the tree, so we can update them as we make changes while at the same
>> time having the branches reflect the reality of the released code.
>> ===
>> Breaking API Changes:
>> * In the bookmark module, renamed "childrenIds" to "children". The
>> data in the property is the same: the name was a typo before, it
>> contained whole values, not just ids.
On Mon, Jul 6, 2009 at 4:28 PM, Colin Bleckner<co...@xmarks.com> wrote:
> Looks like 3.0.191.3 was just pushed out, I just started getting errors in
> my bookmark code a few minutes ago. :) Changing childrenIds to children got
> everything happy again.
> - Colin
> Aaron Boodman wrote:
> I should have said in the title:
> These are the visible changes for 3.0.191.x, which should start
> showing up today or tomorrow.
> - a
> On Thu, Jul 2, 2009 at 1:24 AM, Aaron Boodman<a...@chromium.org> wrote:
> In the cases where the APIs have changed, I'm going to hold off
> updating the docs until the release gets pushed. That way the docs
> reflect the current reality. Soon, we hope to have docs checked into
> the tree, so we can update them as we make changes while at the same
> time having the branches reflect the reality of the released code.
> ===
> Breaking API Changes:
> * In the bookmark module, renamed "childrenIds" to "children". The
> data in the property is the same: the name was a typo before, it
> contained whole values, not just ids.
