I don't think it's justified now that for just 2 external applications we have another repository. The release process will be harder and the versioning confusing. But we should provide a model for other community contributed Flavors on how they should organize their Flavor repository.
Thanks, Caty On Mon, Jun 26, 2017 at 10:59 AM, Thomas Mortagne <[email protected] > wrote: > This is a bad idea IMO. When we talked about that the releases were a > lot less frequent they are now. > > On Sat, Jun 24, 2017 at 2:46 PM, Vincent Massol <[email protected]> > wrote: > > Hi devs, > > > > Part 1 > > ===== > > > > I was looking at http://dev.xwiki.org/xwiki/bin/view/Community/ > DevelopmentPractices#HTopLevelExtensions and found the thread where it > was voted in July 2014: > > http://markmail.org/message/4hglttljiio5v2km > > > > Does anyone remember the thread were we decided to not do it? > > > > I also found this VOTEd thread from 21st June 2016: > http://markmail.org/message/rb5xuex3mpzg3lsm > > > > This new thread is not contradictory with http://markmail.org/message/ > 4hglttljiio5v2km so it doesn’t supersedes it. Thus there really must be > some other thread where we decided to not implement > http://dev.xwiki.org/xwiki/bin/view/Community/DevelopmentPractices# > HTopLevelExtensions. > > > > Part 2 > > ===== > > > > Now, about http://markmail.org/message/4hglttljiio5v2km we have almost > implemented it. We’re just missing one point: > > > > “ > > * The Default Flavor would have at least the same release cycle as the > base > > flavor but it could have more releases (if some of the bundled > third-party > > extensions has some important bug fixes or new features that we want to > offer > > quickly without waiting for the next base flavor release). > > “ > > > > And later on: > > > > “ > > Technically this means putting the Default Flavor in a > > separate github repo (same as xwiki-enterprise being in a separate > repo). We > > need to discuss how we do it: > > - consider it’s XE for now and just add the 2 deps of Tour and CK to XE > > - introduce a new repo for the default flavor and do the build for it and > > > > deprecate XE in favor of it. For now we probably need to hardcode the > flavor id > > in the platform WAR till we’re ready to have the flavor selection screen > at > > startup (and for HSQLDB/Jetty packaging we need a hard-coded flavor > anyway). > > " > > > > Right now we’ve put the “Standard Flavor” (that’s the new name) inside > xwiki-platform but we discussed back then move it to a separate repo in the > xwiki github organization and have only the base flavor in platform. > > > > Should we do what we decided? > > > > Thanks > > -Vincent > > > > > > -- > Thomas Mortagne >
