On Wednesday, June 18, 2014 2:12:47 PM UTC+1, mambu wrote:
>
> Hi,
>
> Just to clarify, what do you mean with "upstream"? Is it the main Jenkins 
> branch or is there a new branch for this changes?
>

The upstream Jenkins repo at https://github.com/jenkinsci/jenkins
 

> Have you tried any plugins that rely on tables to see what happens? How do 
> we coordinate for updating plugins to get work without parent tables?
>

I assume you are talking about the changes we're looking at making to the 
config pages i.e. getting rid of tables and replacing with divs?  This will 
undoubtedly have an effect on plugins, quite a few of which seem to be 
using tables - I wrote a simple script to pull all repos (numbering ~ 690) 
and grep'd across them... there were quite a few tables.  We need to figure 
out a best strategy for this but yes, there will be side effects and we'll 
try minimize them as best we can.

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

Reply via email to