librelist archives

« back to archive

Shoes 3.2 Release - Call for Issues

Shoes 3.2 Release - Call for Issues

From:
Peter Fitzgibbons
Date:
2012-03-23 @ 03:20
HI Folks,

We've all been working hard on the next release for shoes.
At the same time, Steve is taking a 90% personal leave from the project to
take care of family.
Steve and I have discussed and I am here to serve as interim leader.

With that said, we have two milestones to itemize.

1. Tasks for 3.2 release.   This release (yet to be code-named) is a
modernization release to allow correct building and packaging for Window
7,8 and some update dependencies.
2. Update shoesrb.com with new GitHub based web.  When we have achieved
some level of "completion", Steve or I will post it to Heroku's shoesrb.comnode.

Anyone that has tasks, started, in-work, completed, that are issues that
need to be included in 3.2, please ensure that you have created issues in
GitHub Shoes (https://github.com/shoes/shoes/issues).  We will start
tracking our progress to 3.2 with the issue list.  I created Milestone
3.2.   Please link your tasks to that.  If you ahve existing issues, please
link them to milestone 3.2.

Shoes On

Peter Fitzgibbons
(847) 859-9550
Email: peter.fitzgibbons@gmail.com
IM GTalk: peter.fitzgibbons
IM AOL: peter.fitzgibbons@gmail.com

Re: [shoes] Shoes 3.2 Release - Call for Issues

From:
Jirapong Nanta
Date:
2012-03-23 @ 03:42
Hi,
  Please assign this to me (https://github.com/shoes/shoes/issues/179). I
will start to work on it.

Best,
-Jirapong

On Fri, Mar 23, 2012 at 10:20 AM, Peter Fitzgibbons <
peter.fitzgibbons@gmail.com> wrote:

> HI Folks,
>
> We've all been working hard on the next release for shoes.
> At the same time, Steve is taking a 90% personal leave from the project to
> take care of family.
> Steve and I have discussed and I am here to serve as interim leader.
>
> With that said, we have two milestones to itemize.
>
> 1. Tasks for 3.2 release.   This release (yet to be code-named) is a
> modernization release to allow correct building and packaging for Window
> 7,8 and some update dependencies.
> 2. Update shoesrb.com with new GitHub based web.  When we have achieved
> some level of "completion", Steve or I will post it to Heroku's
> shoesrb.com node.
>
> Anyone that has tasks, started, in-work, completed, that are issues that
> need to be included in 3.2, please ensure that you have created issues in
> GitHub Shoes (https://github.com/shoes/shoes/issues).  We will start
> tracking our progress to 3.2 with the issue list.  I created Milestone
> 3.2.   Please link your tasks to that.  If you ahve existing issues, please
> link them to milestone 3.2.
>
> Shoes On
>
> Peter Fitzgibbons
> (847) 859-9550
> Email: peter.fitzgibbons@gmail.com
> IM GTalk: peter.fitzgibbons
> IM AOL: peter.fitzgibbons@gmail.com
>

Re: [shoes] Shoes 3.2 Release - Call for Issues

From:
Tobias Pfeiffer
Date:
2012-03-23 @ 16:54
Hi Peter,

thanks for doing this!

Well Ash's pull request will have to be merged: 
https://github.com/shoes/shoes/pull/185 for the whole Windows stuff and 
also a commit by me that fixes a problem with rubygems not working. My 
commit should affect all versions since this was a change in the 
rubygems version were they call a method that we simply didn't implement 
before.
The sooner this merge can happen the better, before the impl diverges more.

Personally I will open an issue about rubygems deprecations, but as it 
still seems to work it shouldn't be a release blocker. People just get 
swamped with deprecation warnings when installing gems. Many of them are 
deprecated without a replacement so getting the stuff right could take 
quite some time but I'll try to do it.

Cheers,
Tobi (back in germany, yay!)

On 03/23/2012 04:20 AM, Peter Fitzgibbons wrote:
> HI Folks,
>
> We've all been working hard on the next release for shoes.
> At the same time, Steve is taking a 90% personal leave from the 
> project to take care of family.
> Steve and I have discussed and I am here to serve as interim leader.
>
> With that said, we have two milestones to itemize.
>
> 1. Tasks for 3.2 release.   This release (yet to be code-named) is a 
> modernization release to allow correct building and packaging for 
> Window 7,8 and some update dependencies.
> 2. Update shoesrb.com <http://shoesrb.com> with new GitHub based web.  
> When we have achieved some level of "completion", Steve or I will post 
> it to Heroku's shoesrb.com <http://shoesrb.com> node.
>
> Anyone that has tasks, started, in-work, completed, that are issues 
> that need to be included in 3.2, please ensure that you have created 
> issues in GitHub Shoes (https://github.com/shoes/shoes/issues).  We 
> will start tracking our progress to 3.2 with the issue list.  I 
> created Milestone 3.2.   Please link your tasks to that.  If you ahve 
> existing issues, please link them to milestone 3.2.
>
> Shoes On
>
> Peter Fitzgibbons
> (847) 859-9550
> Email: peter.fitzgibbons@gmail.com <mailto:peter.fitzgibbons@gmail.com>
> IM GTalk: peter.fitzgibbons
> IM AOL: peter.fitzgibbons@gmail.com <mailto:peter.fitzgibbons@gmail.com>

Re: [shoes] Shoes 3.2 Release - Call for Issues

From:
Peter Fitzgibbons
Date:
2012-03-23 @ 19:53
HI Tobi and Ash,

Are both of your fixes tied to Issues in Github?  If not, could you create
an associated issue so I can track done-ness?

I'm going to be wanting to clean up the issue list next week and get a
stable list of items to resolve for 3.2 release.

Thanks!

Peter Fitzgibbons
(847) 859-9550
Email: peter.fitzgibbons@gmail.com
IM GTalk: peter.fitzgibbons
IM AOL: peter.fitzgibbons@gmail.com


On Fri, Mar 23, 2012 at 11:54 AM, Tobias Pfeiffer <
tobias.pfeiffer@student.hpi.uni-potsdam.de> wrote:

> **
> Hi Peter,
>
> thanks for doing this!
>
> Well Ash's pull request will have to be merged:
> https://github.com/shoes/shoes/pull/185 for the whole Windows stuff and
> also a commit by me that fixes a problem with rubygems not working. My
> commit should affect all versions since this was a change in the rubygems
> version were they call a method that we simply didn't implement before.
> The sooner this merge can happen the better, before the impl diverges more.
>
> Personally I will open an issue about rubygems deprecations, but as it
> still seems to work it shouldn't be a release blocker. People just get
> swamped with deprecation warnings when installing gems. Many of them are
> deprecated without a replacement so getting the stuff right could take
> quite some time but I'll try to do it.
>
> Cheers,
> Tobi (back in germany, yay!)
>
>
> On 03/23/2012 04:20 AM, Peter Fitzgibbons wrote:
>
> HI Folks,
>
> We've all been working hard on the next release for shoes.
> At the same time, Steve is taking a 90% personal leave from the project to
> take care of family.
> Steve and I have discussed and I am here to serve as interim leader.
>
> With that said, we have two milestones to itemize.
>
> 1. Tasks for 3.2 release.   This release (yet to be code-named) is a
> modernization release to allow correct building and packaging for Window
> 7,8 and some update dependencies.
> 2. Update shoesrb.com with new GitHub based web.  When we have achieved
> some level of "completion", Steve or I will post it to Heroku's
> shoesrb.com node.
>
> Anyone that has tasks, started, in-work, completed, that are issues that
> need to be included in 3.2, please ensure that you have created issues in
> GitHub Shoes (https://github.com/shoes/shoes/issues).  We will start
> tracking our progress to 3.2 with the issue list.  I created Milestone
> 3.2.   Please link your tasks to that.  If you ahve existing issues, please
> link them to milestone 3.2.
>
> Shoes On
>
> Peter Fitzgibbons
> (847) 859-9550
> Email: peter.fitzgibbons@gmail.com
> IM GTalk: peter.fitzgibbons
> IM AOL: peter.fitzgibbons@gmail.com
>
>
>

Re: [shoes] Shoes 3.2 Release - Call for Issues

From:
Tobias Pfeiffer
Date:
2012-03-24 @ 09:54
Hi Peter,

my fix is tied to one but apparently Michal Papis already fixed it (and 
the deprecation warnings) on develop. It's this issue: 
https://github.com/shoes/shoes/issues/189#issuecomment-4664055

As pull requests are issues themselves, Ash's pull request is an issue 
and can be found here: https://github.com/shoes/shoes/pull/185 Eric was 
already so nice to say to give this merge a try :-)

Cheers,
Tobi

On 03/23/2012 08:53 PM, Peter Fitzgibbons wrote:
> HI Tobi and Ash,
>
> Are both of your fixes tied to Issues in Github?  If not, could you 
> create an associated issue so I can track done-ness?
>
> I'm going to be wanting to clean up the issue list next week and get a 
> stable list of items to resolve for 3.2 release.
>
> Thanks!
>
> Peter Fitzgibbons
> (847) 859-9550
> Email: peter.fitzgibbons@gmail.com <mailto:peter.fitzgibbons@gmail.com>
> IM GTalk: peter.fitzgibbons
> IM AOL: peter.fitzgibbons@gmail.com <mailto:peter.fitzgibbons@gmail.com>
>
>
> On Fri, Mar 23, 2012 at 11:54 AM, Tobias Pfeiffer 
> <tobias.pfeiffer@student.hpi.uni-potsdam.de 
> <mailto:tobias.pfeiffer@student.hpi.uni-potsdam.de>> wrote:
>
>     Hi Peter,
>
>     thanks for doing this!
>
>     Well Ash's pull request will have to be merged:
>     https://github.com/shoes/shoes/pull/185 for the whole Windows
>     stuff and also a commit by me that fixes a problem with rubygems
>     not working. My commit should affect all versions since this was a
>     change in the rubygems version were they call a method that we
>     simply didn't implement before.
>     The sooner this merge can happen the better, before the impl
>     diverges more.
>
>     Personally I will open an issue about rubygems deprecations, but
>     as it still seems to work it shouldn't be a release blocker.
>     People just get swamped with deprecation warnings when installing
>     gems. Many of them are deprecated without a replacement so getting
>     the stuff right could take quite some time but I'll try to do it.
>
>     Cheers,
>     Tobi (back in germany, yay!)
>
>
>     On 03/23/2012 04:20 AM, Peter Fitzgibbons wrote:
>>     HI Folks,
>>
>>     We've all been working hard on the next release for shoes.
>>     At the same time, Steve is taking a 90% personal leave from the
>>     project to take care of family.
>>     Steve and I have discussed and I am here to serve as interim leader.
>>
>>     With that said, we have two milestones to itemize.
>>
>>     1. Tasks for 3.2 release.   This release (yet to be code-named)
>>     is a modernization release to allow correct building and
>>     packaging for Window 7,8 and some update dependencies.
>>     2. Update shoesrb.com <http://shoesrb.com> with new GitHub based
>>     web.  When we have achieved some level of "completion", Steve or
>>     I will post it to Heroku's shoesrb.com <http://shoesrb.com> node.
>>
>>     Anyone that has tasks, started, in-work, completed, that are
>>     issues that need to be included in 3.2, please ensure that you
>>     have created issues in GitHub Shoes
>>     (https://github.com/shoes/shoes/issues).  We will start tracking
>>     our progress to 3.2 with the issue list.  I created Milestone
>>     3.2.   Please link your tasks to that.  If you ahve existing
>>     issues, please link them to milestone 3.2.
>>
>>     Shoes On
>>
>>     Peter Fitzgibbons
>>     (847) 859-9550 <tel:%28847%29%20859-9550>
>>     Email: peter.fitzgibbons@gmail.com
>>     <mailto:peter.fitzgibbons@gmail.com>
>>     IM GTalk: peter.fitzgibbons
>>     IM AOL: peter.fitzgibbons@gmail.com
>>     <mailto:peter.fitzgibbons@gmail.com>
>
>

Re: [shoes] Shoes 3.2 Release - Call for Issues

From:
Cecil Coupe
Date:
2012-03-23 @ 04:32
Would this be the correct time and place to mention that Shoes
(pack.rb), the rakefiles, the platform specific stub files that run at
install and the website(s) involved don't know how to to do 3.2 (or the
missing 3.1). They only know "Policeman" or Shoes3.exe. Shoes3.dmg,
Shoes3.run. They know nothing about 3.0, 3.1, 3.2,  or 32/64 bit
versions. 

FWIW, amongst the old timers on the ML, the next Shoes was to be called
'Walkabout' but way back then we hoped to have VLC functionality
restored to what Raisin would do and a more robust/useful/documented
widget. But, that was back then.

I applaud the effort to update the website(s) but I caution that you
have to tell (edit/compile) Shoes so it knows about them.

It would be helpful to actually fix, test and close the issues we have
reported. Otherwise, we've just dancing with the rake files and gem
handling to make developers happy and not fixing user problems. 

Carry on,
--Cecil



On Thu, 2012-03-22 at 22:20 -0500, Peter Fitzgibbons wrote:
> HI Folks,
> 
> We've all been working hard on the next release for shoes.
> At the same time, Steve is taking a 90% personal leave from the
> project to take care of family.
> Steve and I have discussed and I am here to serve as interim leader.
> 
> With that said, we have two milestones to itemize.
> 
> 1. Tasks for 3.2 release.   This release (yet to be code-named) is a
> modernization release to allow correct building and packaging for
> Window 7,8 and some update dependencies.
> 2. Update shoesrb.com with new GitHub based web.  When we have
> achieved some level of "completion", Steve or I will post it to
> Heroku's shoesrb.com node.
> 
> Anyone that has tasks, started, in-work, completed, that are issues
> that need to be included in 3.2, please ensure that you have created
> issues in GitHub Shoes (https://github.com/shoes/shoes/issues).  We
> will start tracking our progress to 3.2 with the issue list.  I
> created Milestone 3.2.   Please link your tasks to that.  If you ahve
> existing issues, please link them to milestone 3.2.
> 
> Shoes On
> 
> Peter Fitzgibbons
> (847) 859-9550
> Email: peter.fitzgibbons@gmail.com
> IM GTalk: peter.fitzgibbons
> IM AOL: peter.fitzgibbons@gmail.com

Re: [shoes] Shoes 3.2 Release - Call for Issues

From:
Eric Watson
Date:
2012-03-24 @ 06:28
On Mar 22, 2012, at 11:32 PM, Cecil Coupe <ccoupe@cableone.net> wrote:

> Would this be the correct time and place to mention that Shoes
> (pack.rb), the rakefiles, the platform specific stub files that run at
> install and the website(s) involved don't know how to to do 3.2 (or the
> missing 3.1). They only know "Policeman" or Shoes3.exe. Shoes3.dmg,
> Shoes3.run. They know nothing about 3.0, 3.1, 3.2,  or 32/64 bit
> versions. 

Yes, I believe this is the correct time. Do you think we can get by with 
the current naming/numbering system? Do we have separate 32/64 bit builds 
for Linux?

> FWIW, amongst the old timers on the ML, the next Shoes was to be called
> 'Walkabout' but way back then we hoped to have VLC functionality
> restored to what Raisin would do and a more robust/useful/documented
> widget. But, that was back then.

I vote to keep the name Walkabout. 

> 
> I applaud the effort to update the website(s) but I caution that you
> have to tell (edit/compile) Shoes so it knows about them.

If I recall, we don't need the Shoes downloads to live on the website, 
though. We just have to provide URLs on the website that return the URLs 
for the downloads (which could be on github, for instance)

> It would be helpful to actually fix, test and close the issues we have
> reported. Otherwise, we've just dancing with the rake files and gem
> handling to make developers happy and not fixing user problems.

Agreed. Guilty. I addressed my first outstanding issue today (merging 
windows fixes back into develop branch) :)

Eric

Re: [shoes] Shoes 3.2 Release - Call for Issues

From:
Cecil Coupe
Date:
2012-03-24 @ 10:53
On Sat, 2012-03-24 at 01:28 -0500, Eric Watson wrote:
> On Mar 22, 2012, at 11:32 PM, Cecil Coupe <ccoupe@cableone.net> wrote:
> 
>  Do you think we can get by
> with the current naming/numbering system? Do we have separate 32/64 bit
> builds for Linux?

Actually, bug fixes or maintenance releases just require doing the 'rake
install' or 'rake package' or 'rake stub' ( I don't remember which at
the moment) and then upload the shoes-r1xyz.exe|dmg ) to replace
Shoes3.exe or Shoes3.dmg. Odds are high that the binaries there now are
not the binaries from a year ago when Policeman was released. 

For example, ashbb can copy any shoes-rxyz.exe he likes to
rin-sun.com/x/y/shoes3.exe. That is seriously good. He doesn't need 3.1
or 3.2 pronouncements or permissions to issue a bug fixed binary. Nor
did you when fixing the dmg packaging. Odds are high that the Linux
Shoes3.run is not built on the same source code as yours or ashbb's or
mine.

IMO, Policeman 3.x shouldn't have a Linux download at all, 32 or 64.
Build it from source. That is not a popular opinion. Reasonable people
may disagree, and they did.

> > FWIW, amongst the old timers on the ML, the next Shoes was to be
> called > 'Walkabout' but way back then we hoped to have VLC
> functionality > restored to what Raisin would do and a more
> robust/useful/documented > widget. But, that was back then.
> 
> I vote to keep the name Walkabout. 
> 
> > > I applaud the effort to update the website(s) but I caution that
> you > have to tell (edit/compile) Shoes so it knows about them.
> 
> If I recall, we don't need the Shoes downloads to live on the website,
> though. We just have to provide URLs on the website that return the
> URLs for the downloads (which could be on github, for instance)

Correct. The Shoes master site returns the url line (from a file?) when
the run time stub asks for it. The binary could be anywhere.  Think
about the popular open source projects. They offer a long list of
binaries to download for all kinds of machine/os architecture.  Easy
enough to do on the Shoes website and pages, just add list items and
urls to download Ubuntu 11.4/64 and Ubuntu 11.10/32 or OSX 10.6
Universal or 10.7 Lion 64 or Windows 7, 32 and 64 or Windows 8, 32 and
64. Easy to do on a webpage list of downloads available. 

[deleted a lot of my O/T half baked speculation about how to package
Shoes scripts without the circuitous burden of binject and packager. I
have a vision that might work for Red Shoes and Green Shoes but this not
the place or time to hijack threads. Focus on the near term task, Cecil]

> 
> > It would be helpful to actually fix, test and close the issues we
> have > reported. Otherwise, we've just dancing with the rake files and
> gem > handling to make developers happy and not fixing user problems.
> 
> Agreed. Guilty. I addressed my first outstanding issue today (merging
> windows fixes back into develop branch) :)

Yup, I closed one of my own trivial issues before I whined to the ML.
Fix them or retract them.  We need to get every one on the same source
version and test to see what is broken on the combined tree,

  I need to write up a decent whine about green shoes and red shoes
using the same ~/.shoes/gems directory but that is for another day. See
http://werehosed.wordpress.com/2012/03/24/a-fred-browser-written-in-shoes/
for background,


Re: [shoes] Shoes 3.2 Release - Call for Issues

From:
Steve Klabnik
Date:
2012-03-23 @ 13:14
To assist with this, I've made _all_ of Team Shoes administrators of
the shoes repo, at least. So anyone can do whatever administrative
work they'd like, including assigning issues, opening and closing
things, editing text... I trust that nobody will do anything stupid.
It's hard to read tone over the internet, so please read that as a
statement, and not as some kind of jerkish "I **TRUST** that nobody
will screw it up, hmmmm?" implication. <3

Re: [shoes] Shoes 3.2 Release - Call for Issues

From:
Peter Fitzgibbons
Date:
2012-03-23 @ 13:51
Implied or otherwise,
I'll take due caution.
:)

Peter Fitzgibbons
Sent from my iPhone

On Mar 23, 2012, at 8:17 AM, Steve Klabnik <steve@steveklabnik.com> wrote:

> To assist with this, I've made _all_ of Team Shoes administrators of
> the shoes repo, at least. So anyone can do whatever administrative
> work they'd like, including assigning issues, opening and closing
> things, editing text... I trust that nobody will do anything stupid.
> It's hard to read tone over the internet, so please read that as a
> statement, and not as some kind of jerkish "I **TRUST** that nobody
> will screw it up, hmmmm?" implication. <3

Re: [shoes] Shoes 3.2 Release - Call for Issues

From:
Steve Klabnik
Date:
2012-03-23 @ 13:15
> I applaud the effort to update the website(s) but I caution that you
> have to tell (edit/compile) Shoes so it knows about them.

Yeah, I still need to source dive to figure this out. The current site
is just a wget mirror of the existing one.