Lighthouse query for what's remaining in 2.3.3?

Is there a particular ticket view or query for seeing what's left to
do on a given release? I'm interested in 2.3.3 at the moment, but I
think in general it would be very helpful to see what tickets are
considered in play for a given point release and what remains open.

I'm not talking about edge rails, but just whenever there are point
releases on the horizon.

Thanks!
Jeff

Is there a particular ticket view or query for seeing what's left to
do on a given release? I'm interested in 2.3.3 at the moment, but I
think in general it would be very helpful to see what tickets are
considered in play for a given point release and what remains open.

Sadly no, lighthouse is in a bit of a state right now and one thing I
think we need to seriously work on is categorising and triaging of
tickets.

I've marked the two I'm considering blockers for this report:

https://rails.lighthouseapp.com/projects/8994/milestones/41795-233

The best way to help right now is to go through tickets and if they
look like they should be a blocker, reply to this thread with the
message. The criteria for blocking this point release should be:

* Breaks something which worked in 2.3.2 (automatically a blocker)
* Fixes something broken from 2.2.2 (probably a blocker)

I'm not talking about edge rails, but just whenever there are point
releases on the horizon.

There's one on the horizon now and those two tickets are blockers. If
anyone finds themselves with a few spare hours. Go through the
tickets and help us find any others.

> Is there a particular ticket view or query for seeing what's left to
> do on a given release? I'm interested in 2.3.3 at the moment, but I
> think in general it would be very helpful to see what tickets are
> considered in play for a given point release and what remains open.

Sadly no, lighthouse is in a bit of a state right now and one thing I
think we need to seriously work on is categorising and triaging of
tickets.

I've marked the two I'm considering blockers for this report:

https://rails.lighthouseapp.com/projects/8994/milestones/41795-233

Thanks Koz, that's helpful to see.

The best way to help right now is to go through tickets and if they
look like they should be a blocker, reply to this thread with the
message. The criteria for blocking this point release should be:

* Breaks something which worked in 2.3.2 (automatically a blocker)
* Fixes something broken from 2.2.2 (probably a blocker)

Should we use the "2.x" tag to see all the tickets? If so, I tried
that but get a Lighthouse error page (https://rails.lighthouseapp.com/
projects/8994/milestones/9903-2-x). Hopefully it will be fixed before
you even see this message.

Or is there a better way to look at all the tickets that should be
reviewed to see if there are any other blockers for 2.3.3?

Thanks again,

Jeff

Hi,
May I suggest this one? http://rails.lighthouseapp.com/projects/8994/tickets/2251

Please look at the bottom of the comments list, my patch has spotlighted another bug, but the resolution is controversy, due to opposite behaviors allowed to the hmt association.

I found a TODO in the concerned portion of code, but I'm a bit confused about the policy we want to apply, on the other hand, many people hit this bug, when vendored the 2-3-stable branch.

Cheers,
Luca

I just posted a rollup ticket (#2773) for a bunch of small fixes to the config.gem stuff.

https://rails.lighthouseapp.com/projects/8994-ruby-on-rails/tickets/2773

Most of what that patch covers were regressions in 2.3.2 from previous behavior.

On a related note, it would be nice to get in #2682 (makes a better error message when dependencies are missing) and #1757 (loads generators correctly from vendor/gems). The latter isn't a regression, as it hasn't ever worked right before... :slight_smile:

Finally, on a thoroughly *unrelated* note, the patch from #1703 would be nice, if only to stop it being reported over and over. There have been quite a few duplicates of that ticket.

--Matt Jones

It seems the 2.3.3 milestone has been removed, and now there's a 2.3.4
milestone? Will 2.3.3 not be released after all?

Any idea of a timeframe for 2.3.4? There are bugs from 2.3.2 that
have been fixed for some time, and it would be nice to get those out
the door.

You know, before 3.0 is released :slight_smile:

I don't use IRC as much as I should, so I apologize if these questions
were already answered there.

Thanks,
Jeff

> Is there a particular ticket view or query for seeing what's left to
> do on a given release? I'm interested in2.3.3 at the moment, but I
> think in general it would be very helpful to see what tickets are
> considered in play for a given point release and what remains open.

Sadly no,lighthouseis in a bit of a state right now and one thing I
think we need to seriously work on is categorising and triaging of
tickets.

I've marked the two I'm considering blockers for this report:

https://rails.lighthouseapp.com/projects/8994/milestones/41795-233

It seems the 2.3.3 milestone has been removed, and now there's a 2.3.4
milestone? Will 2.3.3 not be released after all?

I'm just waiting on some release note information. The code is
'done', I'll be tagging and pushing it in the next few days.

Any idea of a timeframe for 2.3.4? There are bugs from 2.3.2 that
have been fixed for some time, and it would be nice to get those out
the door.

Agreeed, 2.3.4 will be 6 weeks after 2.3.3, I'm planning to do them
every 6 weeks from now until 3.0 ships (assuming there's something
pending in master).

Awesome - and thanks again.

Jeff