On Thu, Jun 12, 2014 at 11:13 AM, Rob Petti <[email protected]> wrote:
> publish to the beta update center under
> the same namespace, though I admit some ignorance as to how that would work
> with the release plugins and tagging.
I think everything would “just work” if (1) the new code is in a
branch such as ‘v2’, (2) it uses a newer version, and (3) that new
version includes ‘beta’ in the name: so start with
2.0-beta-1-SNAPSHOT. You can still cut 1.x releases from the ‘master’
branch as usual, but if you
git checkout v2 && mvn -B release:{prepare,perform}
then you will produce 2.0-beta-1, 2.0-beta-2, etc. tagged
appropriately on the branch and visible only on the experimental
update center. maven-release-plugin is smart enough to stay on the
current branch, and update only the last numeric component. If and
when you want to switch to v2 for real, just merge to master, change
2.0-beta-<n>-SNAPSHOT to 2.0-SNAPSHOT, and release.
--
You received this message because you are subscribed to the Google Groups
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
