Re: LT 0.8.2 proposal

2016-09-05 Thread Michael Ball
It would seem to me that we shouldn't be working on stuff like vertical tab 
splitting or shell in tab, when we have a huge blocking issue issue that's 
holding back a ton of high value features and more community participation.

https://github.com/LightTable/LightTable/issues/1973


I'm not sure, but according to the comments it's preventing us from using 
clojure.test for tests as well as parinfer.

My preference would be for a LightTable 0.9.0 release solely focused just 
on upgrading to clojurescript 1.9.




On Monday, August 29, 2016 at 10:08:29 AM UTC-7, fun...@gmail.com wrote:
>
>
>- fix issues that are in progress 
>
> 
>  
>(currently 3)
>- fix one of the top 2 features requested by users 
> (#662 
> or #533 
>)
>- list all issues and PRs that were fixed since 0.8.1 (that can be 
>done automatically) in the changelog
>- review the queued PRs that are in progress 
>
> 
>  
>(currently 5)
>- move some issues from 0.9 to a new 0.8.3 milestone
>- add a candidate-next* label for futur milestones
>- create a release checklist wiki page on Github
>
> This seems doable to me but Id like to have some feedback:
>
>1. Should we add more?
>2. Are you supporting a rapid release cycle? (less issues fixed but 
>frequent releases)
>3. Should 0.8.2 have even less? If so what should be moved to 0.8.3?
>4. Out of these tasks what are the ones you want to be assigned to?
>
>
> * on that type of issues once you have two +1 and one champion it gets 
> added to the next milestone (inspired by ESLint guidelines)
>
>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Light Table Discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to light-table-discussion+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: LT 0.8.2 proposal

2016-09-03 Thread funcod

>
> we need to achieve consensus somehow, or change or replace our conventions 
> for the project
>

You don't need to do them all. One would be fine, as a start, and maybe 
establishing that we can't have more than X PRs queued. Or a monthly review 
day, e.g. the first Sunday of the first week.

 …whenever we (the core team) decide we want to publish a new release 
> (whenever that is).
>

What are your criteria?

 I'm not willing to commit to something like this.
>

It was just a proposal. 

-- 
You received this message because you are subscribed to the Google Groups 
"Light Table Discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to light-table-discussion+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.