Reacting to both replies: I have set up another job, ready to go - the Maven Way (tm) :-P - but making that new 'release' job's artefacts available to testers through the Installer would mean tweaking the Installer config. I'd rather not do that, I'm trying to keep this release as simple as possible and avoid any unnecessary interaction with the Installer.
EdB On Wed, Nov 19, 2014 at 5:38 PM, Christofer Dutz <christofer.d...@c-ware.de> wrote: > How about doing it the maven way? ;-) > > At the day of the release branch, keep the version in the release branch > and increment the version of develop. > Create a second Jenkins job. One building the release branch and one the > develop. Having the Installer give the user 2 options. "Release Build > SNAPSHOT" or "develop SNAPSHOT". > > Just my 50ct to this ;-) > > Chris > > > ________________________________________ > Von: Erik de Bruin <e...@ixsoftware.nl> > Gesendet: Mittwoch, 19. November 2014 17:01 > An: dev@flex.apache.org > Betreff: [SDK] during prep phase, switch 'flex-sdk-release' to release > branch > > Hi, > > I'm looking for ideas or alternate viewpoints on the following: I plan to > switch the 'flex-sdk-release' job, which produces the Nightly Builds, to > the release branch, as soon as I cut one for the upcoming release. The idea > behind this is that we give testers access to the pre-RC release builds > through the Installer, without having to change any settings/configs for > the Installer. > > The develop branch will still be checked through the 'flex-sdk' job, so no > developmental protocol will be lost. > > Does this sound as logical to you as it does to me? Or am I missing > something? > > Thanks, > > EdB > > > > -- > Ix Multimedia Software > > Jan Luykenstraat 27 > 3521 VB Utrecht > > T. 06-51952295 > I. www.ixsoftware.nl > -- Ix Multimedia Software Jan Luykenstraat 27 3521 VB Utrecht T. 06-51952295 I. www.ixsoftware.nl
