Bump version in version.txt [1.0]

[eric-maynard]

With the 1.0 release branch being cut, we should bump this to reflect the current state of main

[snazy]

Let's not use the 1.0.x branch. It's not the branch that's documented in the release guide on the web site.

[eric-maynard]

@snazy I understood that the branch was going to be renamed, are you suggesting that we instead cut a new branch from the tip of main?

[jbonofre]

Sorry, I wasn't clear in my previous comment.

On release branch, it's not a SNAPSHOT, it's a release, so 1.0.0-incubating.

[snazy]

Well, nope. On a tag it's a release version - but not in a branch.

[snazy]

(Otherwise you get a non-reproducible build)

[eric-maynard]

Based on the other branches it looks like it should have no SNAPSHOT but let me know if this does need to change back

[snazy]

@snazy I understood that the branch was going to be renamed, are you suggesting that we instead cut a new branch from the tip of main?

Yep (probably quicker than tweaking an existing PR).

[eric-maynard]

@snazy I'll leave the question of rename vs. new cut to the release manager; my (incorrect?) assumption was that once we've picked a commit to release from we'd prefer not to change that lightly. If we end up closing the target branch here we can cherry pick this onto the new branch 👍

[snazy]

@snazy I'll leave the question of rename vs. new cut to the release manager; my (incorrect?) assumption was that once we've picked a commit to release from we'd prefer not to change that lightly. If we end up closing the target branch here we can cherry pick this onto the new branch 👍

Yea - cherry-picking on the new branch is fine for me. I'd be very careful with removing the -SNAPSHOT suffix in a Git branch - there can be unforeseen consequences.

BTW, if you're interested: Some technical background on semi-automatic releases is here. There are quite some annoying things for releases that can go wrong - most annoying is "concurrent merges/commits" that do happen in real life.

[eric-maynard]

Just changed the target to the new branch release/1.0.x -- thanks guys!

[dimas-b]

I do not think the scope for 1.0 is completely set per dev email thread: https://lists.apache.org/thread/g1m3nj9g7jnrvkd9ogq6h3v4cmll5lwo

Let's hold version updates until we have consensus there.

[eric-maynard]

@dimas-b I have only been loosely following that thread, but it looks like we may be all set now?

[dimas-b]

The question of re-branching from main has been settled, indeed, so I'm ok with merging this PR. No re-branching per: https://lists.apache.org/thread/m4lfwo9lkwjj8gjhqm8no5nhlnd2cdhq

Re: scope, let's use that dev ML thread for any follow-up items.