Can we use "dev" prerelease tag for local builds, rather than "dev.12345.1"?

[dagood]

Right now, a local dev build gives us a version like this: 5.0.0-dev.19569.1. In Core-Setup, this used to be 5.0.0-dev pre-consolidation.

As far as preference goes, I like dev because I can use the same incremental build results over multiple days without any hassle.

With dev.19569.1:

1. I need to rebuild every day, or figure out what MSBuild property to set to let me use the same build across days.
2. I have to figure out what number (date?) to put in to match some earlier build's number (some derivative of date?), if I forgot to override it when running an earlier build.
3. The artifact directory expands over time unless I take action to manually clean up old versions periodically. This also makes it harder to find my actual build artifacts.

Is there an argument for using numbers in the prerelease tag for local builds? Is there a technical reason?

(If there's some hard technical reason, I do think that being the same across all subsets is much more important than making a single subset easier to deal with.)

@dotnet/runtime-infrastructure I'm curious what your thoughts are on this.

[dagood]

In a standup meeting we had today, this came up, and it turns out the daily rebuild requirement is only for the Installer build's usage of the Libraries subset.

[dagood]

Closing: as of #1835, non-CI builds no longer use the date for filenames! 🎉