Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Road to 1.0.0 #216

Closed
1 of 2 tasks
stephenplusplus opened this issue Sep 17, 2014 · 15 comments
Closed
1 of 2 tasks

Road to 1.0.0 #216

stephenplusplus opened this issue Sep 17, 2014 · 15 comments
Assignees
Labels
🚨 This issue needs some love. triage me I really want to be triaged.

Comments

@stephenplusplus
Copy link
Contributor

stephenplusplus commented Sep 17, 2014

What remaining features would we like to offer before we make the jump?

  • API complete for datastore and storage (@ryanseys)
  • To be able to tell users that they'll love it (@ryanseys)
@stephenplusplus stephenplusplus added this to the 1.0.0 milestone Sep 17, 2014
@stephenplusplus
Copy link
Contributor Author

@silvolu @ryanseys @rakyll please go through and tag/create issues with the 1.0.0 milestone.

@rakyll
Copy link
Contributor

rakyll commented Sep 18, 2014

Sorry for missing the big party -- I'm still half offline, half awake :)

Is there any more context about 1.0 versioning? Does it indicate stability and/or API freeze?

@stephenplusplus
Copy link
Contributor Author

Haha, no problem. We had a discussion in the hangout about 1.0.0, and have some differing opinions. I thought we should huddle up so we and the public knows when they can start safely using our project.

Semver lets us be as reckless as we want with our API < 1.0.0, however I propose now that we have more eyes on the project and users trickling in, we should offer more reliability. After some of our bigger issues we tackled (instantiation duality [love this phrase] and dataset.key revamp), I believe we are ready for 1.0.0 (maybe 1.0.0-beta?) and to start incrementing our versions as we add features / fixes accordingly.

If we have more things we want to fit in before 1.0.0, just tag 'em so we're all on the same page.

@stephenplusplus
Copy link
Contributor Author

Does it indicate stability and/or API freeze?

Sorry I didn't catch this specific question the first time. 1.0.0 indicates we won't break the API until 2.0.0. We can add endless features and bug fixes in, but as soon as we have to break backwards compatibility, we must bump 2.0.0. And likewise, we wouldn't want to release 2.0.0 just because we added a hot new feature.

@ryanseys
Copy link
Contributor

I'm against 1.0.0 right now because I know 2.0.0 will be right around the corner and to me, 1.0.0 suggests another celebration & blog post 🍰 . If we're just breaking stuff, even small minor things in small minor ways like .key() and bumping versions because "semver" tells us to, that's bad. The kinks still need to be massaged out, and we also should have feature completeness even in a less-than-optimal way, e.g. ACL for storage, bucket.file(), support for all current api calls for storage and datastore in some way.

What do I want for 1.0.0? I want to be able to tell users that I think they'll love it and that I think they'll find it suits their needs better than google-api-nodejs-client, and that they shouldn't need to update to 2.0.0 for at least 4 months. I kinda just pulled 4 months out of nowhere, but the idea is that we shouldn't have a major version already coming around the mountain.

@ryanseys
Copy link
Contributor

I updated the comment at the top with a couple check-boxes to make it more clear.

@stephenplusplus
Copy link
Contributor Author

Can you tag the issues as well, so we have a clear milestone? It won't only help us, but any curious users who want to know when they can expect stability.

@cristiano-belloni
Copy link
Contributor

As part of (2), do you plan to have a list of projects using gcloud-node? In case, count me in.

@stephenplusplus
Copy link
Contributor Author

Definitely, what's your project?

@cristiano-belloni
Copy link
Contributor

It will be released end of this month / start of Jan. Anyway, it's a web audio editor, next iteration of http://hya.io.
If you are going to provide a list, I can send the project as soon as I release.

@stephenplusplus
Copy link
Contributor Author

That's awesome! Let us know if we can help with anything. We did have a
list, but I think it's in a closed issue now. Will have to dig it up and
tag you over when I find it.

@cristiano-belloni
Copy link
Contributor

Thank you! I'll surely reply here when everything is up.

@stephenplusplus
Copy link
Contributor Author

@janesconference Here it is: #274.

@cristiano-belloni
Copy link
Contributor

Thanks!

@jgeewax jgeewax removed this from the 1.0.0 milestone Feb 2, 2015
@jgeewax
Copy link
Contributor

jgeewax commented Feb 2, 2015

Resolving -- check milestones for Datastore Stable, Storage Stable, and Core Stable to see what's left for 1.0

sofisl pushed a commit that referenced this issue Nov 11, 2022
This PR was generated using Autosynth. 🌈

Synth log will be available here:
https://source.cloud.google.com/results/invocations/f9f34ae0-d83d-4c7a-a197-54a0a7255ebc/targets

- [ ] To automatically regenerate this PR, check this box.

Source-Link: googleapis/synthtool@15013ef
sofisl pushed a commit that referenced this issue Nov 11, 2022
This PR was generated using Autosynth. 🌈

Synth log will be available here:
https://source.cloud.google.com/results/invocations/5f7f9c6d-c75a-4c60-8bb8-0026a14cead7/targets

- [ ] To automatically regenerate this PR, check this box.

PiperOrigin-RevId: 325949033
Source-Link: googleapis/googleapis@94006b3
sofisl pushed a commit that referenced this issue Nov 11, 2022
* chore: update v2.14.2 gapic-generator-typescript

Committer: @summer-ji-eng
PiperOrigin-RevId: 434859890

Source-Link: googleapis/googleapis@bc2432d

Source-Link: googleapis/googleapis-gen@930b673
Copy-Tag: eyJwIjoiLmdpdGh1Yi8uT3dsQm90LnlhbWwiLCJoIjoiOTMwYjY3MzEwM2U5MjUyM2Y4Y2ZlZDM4ZGVjZDdkM2FmYWU4ZWJlNyJ9

* 🦉 Updates from OwlBot post-processor

See https://github.com/googleapis/repo-automation-bots/blob/main/packages/owl-bot/README.md

Co-authored-by: Owl Bot <gcf-owl-bot[bot]@users.noreply.github.com>
sofisl pushed a commit that referenced this issue Nov 11, 2022
- [ ] Regenerate this pull request now.

PiperOrigin-RevId: 439356405

Source-Link: googleapis/googleapis@afa2ba1

Source-Link: googleapis/googleapis-gen@3e40c17
Copy-Tag: eyJwIjoiLmdpdGh1Yi8uT3dsQm90LnlhbWwiLCJoIjoiM2U0MGMxN2UxNTEwYzk1ZmFiNThmYzIxNDNjY2I2MWNjZWNhNTk4OSJ9
sofisl pushed a commit that referenced this issue Nov 11, 2022
Source-Link: googleapis/synthtool@d229a12
Post-Processor: gcr.io/cloud-devrel-public-resources/owlbot-nodejs:latest@sha256:74ab2b3c71ef27e6d8b69b1d0a0c9d31447777b79ac3cd4be82c265b45f37e5e
sofisl pushed a commit that referenced this issue Nov 11, 2022
[![Mend Renovate](https://app.renovatebot.com/images/banner.svg)](https://renovatebot.com)

This PR contains the following updates:

| Package | Change | Age | Adoption | Passing | Confidence |
|---|---|---|---|---|---|
| [jsdoc-fresh](https://togithub.com/googleapis/jsdoc-fresh) | [`^1.0.2` -> `^2.0.0`](https://renovatebot.com/diffs/npm/jsdoc-fresh/1.1.1/2.0.0) | [![age](https://badges.renovateapi.com/packages/npm/jsdoc-fresh/2.0.0/age-slim)](https://docs.renovatebot.com/merge-confidence/) | [![adoption](https://badges.renovateapi.com/packages/npm/jsdoc-fresh/2.0.0/adoption-slim)](https://docs.renovatebot.com/merge-confidence/) | [![passing](https://badges.renovateapi.com/packages/npm/jsdoc-fresh/2.0.0/compatibility-slim/1.1.1)](https://docs.renovatebot.com/merge-confidence/) | [![confidence](https://badges.renovateapi.com/packages/npm/jsdoc-fresh/2.0.0/confidence-slim/1.1.1)](https://docs.renovatebot.com/merge-confidence/) |

---

### Release Notes

<details>
<summary>googleapis/jsdoc-fresh</summary>

### [`v2.0.0`](https://togithub.com/googleapis/jsdoc-fresh/blob/HEAD/CHANGELOG.md#&#8203;200-httpsgithubcomgoogleapisjsdoc-freshcomparev111v200-2022-05-18)

[Compare Source](https://togithub.com/googleapis/jsdoc-fresh/compare/v1.1.1...v2.0.0)

##### ⚠ BREAKING CHANGES

-   update library to use Node 12 ([#&#8203;108](https://togithub.com/googleapis/jsdoc-fresh/issues/108))

##### Build System

-   update library to use Node 12 ([#&#8203;108](https://togithub.com/googleapis/jsdoc-fresh/issues/108)) ([e61c223](https://togithub.com/googleapis/jsdoc-fresh/commit/e61c2238db8900e339e5fe7fb8aea09642290182))

##### [1.1.1](https://www.github.com/googleapis/jsdoc-fresh/compare/v1.1.0...v1.1.1) (2021-08-11)

##### Bug Fixes

-   **build:** migrate to using main branch ([#&#8203;83](https://www.togithub.com/googleapis/jsdoc-fresh/issues/83)) ([9474adb](https://www.github.com/googleapis/jsdoc-fresh/commit/9474adbf0d559d319ff207397ba2be6b557999ac))

</details>

---

### Configuration

📅 **Schedule**: Branch creation - "after 9am and before 3pm" (UTC), Automerge - At any time (no schedule defined).

🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied.

♻ **Rebasing**: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 **Ignore**: Close this PR and you won't be reminded about this update again.

---

 - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, click this checkbox.

---

This PR has been generated by [Mend Renovate](https://www.mend.io/free-developer-tools/renovate/). View repository job log [here](https://app.renovatebot.com/dashboard#github/googleapis/nodejs-analytics-data).
sofisl pushed a commit that referenced this issue Nov 11, 2022
* changes without context

        autosynth cannot find the source of changes triggered by earlier changes in this
        repository, or by version upgrades to tools such as linters.

* chore(nodejs_templates): add script logging to node_library populate-secrets.sh

Co-authored-by: Benjamin E. Coe <bencoe@google.com>

Source-Author: BenWhitehead <BenWhitehead@users.noreply.github.com>
Source-Date: Wed Jun 10 22:24:28 2020 -0400
Source-Repo: googleapis/synthtool
Source-Sha: e7034945fbdc0e79d3c57f6e299e5c90b0f11469
Source-Link: googleapis/synthtool@e703494
sofisl pushed a commit that referenced this issue Nov 11, 2022
[![Mend Renovate](https://app.renovatebot.com/images/banner.svg)](https://renovatebot.com)

This PR contains the following updates:

| Package | Change | Age | Adoption | Passing | Confidence |
|---|---|---|---|---|---|
| [@types/node](https://togithub.com/DefinitelyTyped/DefinitelyTyped/tree/master/types/node) ([source](https://togithub.com/DefinitelyTyped/DefinitelyTyped)) | [`^16.0.0` -> `^18.0.0`](https://renovatebot.com/diffs/npm/@types%2fnode/16.18.3/18.11.9) | [![age](https://badges.renovateapi.com/packages/npm/@types%2fnode/18.11.9/age-slim)](https://docs.renovatebot.com/merge-confidence/) | [![adoption](https://badges.renovateapi.com/packages/npm/@types%2fnode/18.11.9/adoption-slim)](https://docs.renovatebot.com/merge-confidence/) | [![passing](https://badges.renovateapi.com/packages/npm/@types%2fnode/18.11.9/compatibility-slim/16.18.3)](https://docs.renovatebot.com/merge-confidence/) | [![confidence](https://badges.renovateapi.com/packages/npm/@types%2fnode/18.11.9/confidence-slim/16.18.3)](https://docs.renovatebot.com/merge-confidence/) |

---

### Configuration

📅 **Schedule**: Branch creation - "after 9am and before 3pm" (UTC), Automerge - At any time (no schedule defined).

🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied.

♻ **Rebasing**: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 **Ignore**: Close this PR and you won't be reminded about this update again.

---

 - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box

---

This PR has been generated by [Mend Renovate](https://www.mend.io/free-developer-tools/renovate/). View repository job log [here](https://app.renovatebot.com/dashboard#github/googleapis/nodejs-video-transcoder).
<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzMi4yNDEuMTEiLCJ1cGRhdGVkSW5WZXIiOiIzNC4xMS4xIn0=-->
sofisl pushed a commit that referenced this issue Nov 11, 2022
…e in region tag (#216)

PiperOrigin-RevId: 399287285
Source-Link: googleapis/googleapis@1575986
Source-Link: googleapis/googleapis-gen@b27fff6
Copy-Tag: eyJwIjoiLmdpdGh1Yi8uT3dsQm90LnlhbWwiLCJoIjoiYjI3ZmZmNjIzYTVkOGQ1ODZiNzAzYjVlNDkxOTg1NmFiZTdjMmViMyJ9
sofisl pushed a commit that referenced this issue Nov 11, 2022
- [ ] Regenerate this pull request now.

PiperOrigin-RevId: 468790263

Source-Link: googleapis/googleapis@873ab45

Source-Link: googleapis/googleapis-gen@cb6f37a
Copy-Tag: eyJwIjoiLmdpdGh1Yi8uT3dsQm90LnlhbWwiLCJoIjoiY2I2ZjM3YWVmZjJhMzQ3MmU0MGE3YmJhY2U4YzY3ZDc1ZTI0YmVlNSJ9

feat: add `RunAccessReport` method to the Admin API v1alpha
PiperOrigin-RevId: 465589484

Source-Link: googleapis/googleapis@80bf613

Source-Link: googleapis/googleapis-gen@c015f3c
Copy-Tag: eyJwIjoiLmdpdGh1Yi8uT3dsQm90LnlhbWwiLCJoIjoiYzAxNWYzYzcyNWRlNGRlOTAxNWRkODNjNTViMmVjN2ViMDUzMzhkYyJ9

feat: add `GetAudience`, 'ListAudience', 'CreateAudience', 'UpdateAudience', 'ArchiveAudience' methods to the Admin API v1alpha
feat: add `GetAttributionSettings`, `UpdateAttributionSettings` methods to the Admin API v1alpha

PiperOrigin-RevId: 465469599

Source-Link: googleapis/googleapis@2f00b9a

Source-Link: googleapis/googleapis-gen@f4f8a0c
Copy-Tag: eyJwIjoiLmdpdGh1Yi8uT3dsQm90LnlhbWwiLCJoIjoiZjRmOGEwYzA2MzM4NjNkZTk0MTFkM2ExMTBmYTkzZDhlMGE5MzEwNyJ9
sofisl pushed a commit that referenced this issue Nov 16, 2022
This PR was generated using Autosynth. 🌈

Synth log will be available here:
https://source.cloud.google.com/results/invocations/35103ef2-979e-4beb-a5b8-34c85c93e32a/targets

- [ ] To automatically regenerate this PR, check this box.

Source-Link: googleapis/synthtool@901ddd4
Source-Link: googleapis/synthtool@f96d3b4
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🚨 This issue needs some love. triage me I really want to be triaged.
Projects
None yet
Development

No branches or pull requests

6 participants