what keeps me thinking is that there is actually always a difference
between modules that are now part of the main repository and "other"
modules (provided by the larger community), e.g. being a friend to "core"
modules if your are not part of the main tree always seemed very hard
(resulting in a lot of implementation dependencies requiring re-releases
for all major/minor NetBeans versions).
How will we handle this in the new infrastructure at / in Apache? How would
we decide which module ge's in a mega master repository?
I have a gut feeling that we have the chance to / should fix this now.. but
not yet sure how..
Am 12.10.2016 20:31 schrieb "Emilian Bold" <emilian.b...@gmail.com>:
> Yes, I think it makes sense to use branches for 'teams'. Maybe even for
> main-silver, main-golden.
> On Wed, Oct 12, 2016 at 9:23 PM, Vladimir Voskresensky <
> vladimir.voskresen...@oracle.com> wrote:
> > Hi,
> > On 12.10.2016 18:23, Eric Barboni wrote:
> >> With the split in cluster it may possible to get rid of the "team"
> >> repositories (i.e. "core-main","cnd-main","jet-main") but we may need
> >> another repository ( kind of current "main-silver" or "main-golden")
> >> prevent a bad commit leading to compile error in one cluster to be
> >> propagated to the full NetBeans break the build for others who did not
> >> this particular cluster
> > What if we leave one repository as it is now and move 'teams' into git
> > branches (core-main/cnd-main/...).
> > Teams will work on branches.
> > Then like now  the current push-cnd-main job can be replaced by
> > automatic 'push cnd-main into main-silver branch', while push-to-cnd-main
> > job will be automatic 'push main-silver into cnd-main'.
> > Branch main-silver is built and tested as now and on success main-silver
> > is pushed into main-golden for the production build.
> > Thanks,
> > Vladimir.
> >  http://wiki.netbeans.org/HgParallelProjectIntegration