Hi, okay, so I can proceed to make trunk technically releasable. The other task is to review all resolved Jira issues and prepare the release docs. This will take a couple of days anyway.
Do I understand correctly that you would like to make the ng branch the new trunk after the release? Sounds reasonable to me and switching to 1.0-SNAPSHOT, too. Best, - Fabian Am 17.07.2013 15:22 schrieb "Reto Bachmann-Gmür" <r...@wymiwyg.com>: > Hi, > > Right now I'm porting the enhancer to ng. With that we would have the > two most heavily developed components in ng and I think we should move > the ongoing development to the code in that branch. > > So I wanted to propose this after finishing the current porting. This > would mean to have one last release from the pre-ng code and then > switch to the ng-branch and globaly to 1.0.0-SNAPSHOT versions. > > I'd suggest to wait a couple of days till we have the enhancer in ng > and maybe Enrico ported one more component as to be able to see if we > can coordinate this release with the switch to ng. > > Cheers, > Reto > > On Wed, Jul 17, 2013 at 3:01 PM, Fabian Christ > <christ.fab...@googlemail.com> wrote: > > Hi, > > > > time has passed since our last releases at the beginning of 2013. Since > new > > features are under development in different branches we should fix what > we > > have in the trunk. > > > > I propose to prepare a big release of the trunk with all its major > > components. I would exclude the launchers and bundlelists in this > release. > > > > When that is done we should release bundlelists and launcher > configurations > > based on stable (released) components. > > > > I will start to check the trunk for RAT compliance. Once everything is > > checked I would create a release branch. > > > > WDYT? > > > > Best, > > - Fabian >
