Re: [lilycore-dev] Re: /how special formatting idea (PR#431)

[Will C. <wc...@in...>]

Josh Wilmes wrote:
> 
> While porting these things over IS helpful, it does remove some of the
> pressure for ever getting the core to a real "release" state.
> 
> IMHO, there should be planned releases for specific upcoming features, and
> RPI should really be upgrading along with everyone else.  I don't think
> it's good for lily to have RPI running a "weird" core.

These updates are actually part of a plan to get RPI running a non-weird
core.

Because devCore current contains so many unfinished projects, it's not
very useful going forward, because it's unlikely a new release -can- be
cut by those of us remaining.

So, my plan is to take RPI, get rid of all the wierd code (like the /how
code that was special cased for a particular user on RPI that I pulled
today), pull all the updates from devCore that are stable enough (or
small enough) to save, and then archive that devCore.

Then, cut a new core using RPI as the base.

> And if people get whiny (myself included) about some feature which is
> already fixed not being on the RPI core yet, they can do what users on any
> other lily core would do- ask for an upgrade.  This encourages the devcore
> to stay reasonably stable so that releases CAN be made, as well.
> 
> If someone's doing MAJOR surgery which won't be finished in a few days,
> they should do the equivalent of what people do in any other open source
> project.  Check out the core and driver, run it on their own machine, and
> submit a patch.
> 
> Just my 2 cents.

Yup. Agreed.

Comments on my plan of attack more than welcome.