Separating site and code is not enough. Different code requires different levels of maintenance, that's why it's better to separate sandbox and add-ons from trunk too. Sandbox might become outdated or might not compile. It might have a different test or code coverage criteria. It might allow warnings on compilation. Such things tends to spread from unstable\experimental code to cleaner and more stable places. For example, 1 warning stands out and therefore is more likely to be fixed. 5 warnings from sandbox might easily cloud 6th one from trunk.
On 19 August 2016 at 16:21, Richard Eckart de Castilho < richard.eck...@gmail.com> wrote: > Keeping site and code in separate repos: +1 > > -- Richard > > > On 19.08.2016, at 15:17, Anthony Beylerian <anthony.beyler...@gmail.com> > wrote: > > > > @Jörn @Richard > > > > I believe less bloat is always better for code housekeeping. > > For example, although it is small, I think having the site code along > with > > the toolkit code just seems a bit untidy. > > > > How about we at least separate those two? > > It could also be useful to make a more feature rich site in the future. > > > > Actually, the Spark team does that too: > > > > git://git.apache.org/spark.git > > git://git.apache.org/spark-website.git > >
