Hi - SNAPSHOTs are not released to anyone but yourself (or people downloading straight from CI builds) - alpha-beta are visible *only* on experimental update center - regular releases are visible on public update center
If you are new in the dev community, I think you shouldn't worry yourself with alpha/beta. Just use SNAPSHOT, then apply the regular release process using the maven-release-plugin to produce a release version. Vincent 2013/10/10 Mike Caspar <[email protected]> > Hi there, > > I've been watching this thread and looked through the documentation that's > there (and am new the Jenkins Dev Community). > > It seems to me that it makes sense to start using -alpha or -beta, in my > POM. > > What's not clear to me (as a newbie with the group) is the following. > > - Should I deploy a SNAPSHOT *and* an alpha or beta ? > > - Should I switch to just the new naming format and stop publishing > SNAPSHOTS ? > > - It's not 100% clear, but it seems like I might even use > appname-SNAPSHOT-alpha to accomplish both tasks? > > I refer to this page... > > http://jenkins-ci.org/node/439 > > It says ... > > If you are developing plugins and you want to distribute experimental > plugins, all you have to do is to put "alpha" or "beta" in the version > number of pom.xml. The backend infrastructure takes care of the rest. > > Thanks for the help and guidance. > > > > > > -- > 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/groups/opt_out. > -- 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/groups/opt_out.
