In GIT it's pretty easy to just rename the branches. They are nothing more than name refs to different HEADs.
So it's perfectly fine to to the EE8 work in a branch for now and just move it over if we feel fit. LieGrue, strub > Am 08.08.2017 um 22:07 schrieb Jonathan Gallimore > <jonathan.gallim...@gmail.com>: > > I'm ok with this - we do still have some Java EE 7 work and maintenance > going on, so I would want a branch for that at least. I think a tomee-7.x > branch for EE7 and master being used for Java EE 8 could work. > > I like the 8.0 and 8.1 version numbers you propose. We just need to make > that clear in the docs and on the download page. > > Jon > > On Tue, Aug 8, 2017 at 8:20 PM, Mark Struberg <strub...@yahoo.de.invalid> > wrote: > >> Hi folks! >> >> I'd love to start the tomee8 branch. >> There are a lot of components which are ready to go. >> >> And I also had an idea about how we could very eagerly publish binaries to >> play with. >> >> I imagine to have 2 goals: >> >> 1.) TomEE-8.0: this will be the 'development train'. >> It will contain JavaEE8 parts (mostly) and some JavaEE 7 parts still. >> We do not need to wait until we are fully EE8 compatible and certified, we >> can just go on and publish this stuff as long as we CLEARLY state that we >> are not yet fully EE8. >> >> 2.) TomEE-8.1: once we reach full EE8 compatibility we switch over to 8.1. >> >> The main benefit of this approach is that we do not need to wait with >> doing a release until all the features are EE8 but we can eagerly push >> releases which are perfectly fine for people to use already. >> >> >> Wdyt? >> >> LieGrue, >> strub
