Menu
▾
▴
rails-devel
|
From: Stefan F. <ste...@we...> - 2011-09-22 12:20:56
|
All: Brett gave me the permissions, so I will publish a new release 1.5 today. It seems that the main features are: * 18GA complete * 18TN complete * Full support for 1830 Coalfield rights and revenue calculation Anything to add there? For a complete list of changes and bug fixes I will refer to the wiki page. I intend to make bug fix releases in the future (with version numbers 1.x.y) which are published more frequently than the previous 1.x releases. Stefan |
|
From: Chris S. <chr...@gm...> - 2011-09-22 15:52:47
|
There has been discussion on BoardGameGeek of the possibility of having nightly releases, distributed by Dropbox. Any chance of that happening? http://boardgamegeek.com/thread/700675/a-lot-of-tiles-taken-out -- Chris Please consider the environment before printing this e-mail. On Thu, Sep 22, 2011 at 5:23 AM, Stefan Frey <ste...@we...> wrote: > All: > Brett gave me the permissions, so I will publish a new release 1.5 > today. > > It seems that the main features are: > > * 18GA complete > * 18TN complete > * Full support for 1830 Coalfield rights and revenue calculation > > Anything to add there? > > For a complete list of changes and bug fixes I will refer to the wiki page. > > I intend to make bug fix releases in the future (with version numbers 1.x.y) > which are published more frequently than the previous 1.x releases. > > Stefan > > ------------------------------------------------------------------------------ > All the data continuously generated in your IT infrastructure contains a > definitive record of customers, application performance, security > threats, fraudulent activity and more. Splunk takes this data and makes > sense of it. Business sense. IT sense. Common sense. > http://p.sf.net/sfu/splunk-d2dcopy1 > _______________________________________________ > Rails-devel mailing list > Rai...@li... > https://lists.sourceforge.net/lists/listinfo/rails-devel > |
|
From: Stefan F. <ste...@we...> - 2011-09-22 16:30:29
|
Chris: as already stated I like the idea of more frequent builds. However for nightly builds I would prefer an automated setup: To my knowledge there is no public build server for java projects (e.g. using Hudson/Jenkins) yet, but I have never looked actively for something like that. Publishing a build via Dropbox sounds somehow strange, but maybe the right solution for those playing Rails via Dropbox anyway. However I do not volunteer to providing such a solution. But maybe a more frequent publication of bug-fix releases will be a solution, but possibly I should not to give too much promises before I really know how difficult it will be to get the built up to Sourceforge. Stefan On Thursday, September 22, 2011 05:52:40 pm Chris Shaffer wrote: > There has been discussion on BoardGameGeek of the possibility of > having nightly releases, distributed by Dropbox. Any chance of that > happening? > > http://boardgamegeek.com/thread/700675/a-lot-of-tiles-taken-out > > -- > Chris > > Please consider the environment before printing this e-mail. > > On Thu, Sep 22, 2011 at 5:23 AM, Stefan Frey <ste...@we...> wrote: > > All: > > Brett gave me the permissions, so I will publish a new release 1.5 > > today. > > > > It seems that the main features are: > > > > * 18GA complete > > * 18TN complete > > * Full support for 1830 Coalfield rights and revenue calculation > > > > Anything to add there? > > > > For a complete list of changes and bug fixes I will refer to the wiki > > page. > > > > I intend to make bug fix releases in the future (with version numbers > > 1.x.y) which are published more frequently than the previous 1.x > > releases. > > > > Stefan > > > > ------------------------------------------------------------------------- > > ----- All the data continuously generated in your IT infrastructure > > contains a definitive record of customers, application performance, > > security threats, fraudulent activity and more. Splunk takes this data > > and makes sense of it. Business sense. IT sense. Common sense. > > http://p.sf.net/sfu/splunk-d2dcopy1 > > _______________________________________________ > > Rails-devel mailing list > > Rai...@li... > > https://lists.sourceforge.net/lists/listinfo/rails-devel > > --------------------------------------------------------------------------- > --- All the data continuously generated in your IT infrastructure contains > a definitive record of customers, application performance, security > threats, fraudulent activity and more. Splunk takes this data and makes > sense of it. Business sense. IT sense. Common sense. > http://p.sf.net/sfu/splunk-d2dcopy1 > _______________________________________________ > Rails-devel mailing list > Rai...@li... > https://lists.sourceforge.net/lists/listinfo/rails-devel |
|
From: Michał B. <ba...@tl...> - 2011-09-22 16:36:14
|
I could take on the task of providing nightly builds in between releases in a public dropbox folder. I thought a sourceforge site was a better place for it so didn't volunteer, but if this being served on dropbox and not sourceforge I can do it. (I am assuming only patches that have bug fixes would be served publicly, not newly developed stuff). as to your change log for the next release why not mention 1830 wabash is now working? if someone tried playing that and gave up he might be interested it is now working... mike On 11-09-22 18:32, Stefan Frey wrote: > Chris: > as already stated I like the idea of more frequent builds. However for nightly > builds I would prefer an automated setup: To my knowledge there is no public > build server for java projects (e.g. using Hudson/Jenkins) yet, but I have > never looked actively for something like that. > > Publishing a build via Dropbox sounds somehow strange, but maybe the right > solution for those playing Rails via Dropbox anyway. However I do not > volunteer to providing such a solution. > But maybe a more frequent publication of bug-fix releases will be a solution, > but possibly I should not to give too much promises before I really know how > difficult it will be to get the built up to Sourceforge. > > Stefan |
|
From: Erik V. <eri...@xs...> - 2011-09-22 19:50:07
|
> as to your change log for the next release why not mention 1830 wabash is > now working? if someone tried playing that and gave up he might be > interested it is now working... That depends on what you mean with "working". All 1830 variants implemented so far are working, the question is whether or not they are working flawlessly. I cannot assert that for any variant. However, "Fixed all known bugs in 1830 variants" or something like that should certainly be mentioned. I believe all currently implemented variants already existed in the previous version. Erik. |
|
From: Stefan F. <ste...@we...> - 2011-09-22 16:43:41
|
In my understanding the inclusion of new stuff is the defining difference between nightly builds and bug-fix releases to the latest stable release, but opinions might differ here. And I would try for a bug fix release only to apply those changes to the latest stable release which are clear fixes and not new features etc. This is something that the change to git makes much easier to accomplish. Stefan On Thursday, September 22, 2011 06:36:32 pm Michał Bażyński wrote: > I could take on the task of providing nightly builds in between releases > in a public dropbox folder. > I thought a sourceforge site was a better place for it so didn't > volunteer, but if this being served on dropbox and not sourceforge I can > do it. (I am assuming only patches that have bug fixes would be served > publicly, not newly developed stuff). > > as to your change log for the next release why not mention 1830 wabash > is now working? if someone tried playing that and gave up he might be > interested it is now working... > > mike > > On 11-09-22 18:32, Stefan Frey wrote: > > Chris: > > as already stated I like the idea of more frequent builds. However for > > nightly builds I would prefer an automated setup: To my knowledge there > > is no public build server for java projects (e.g. using Hudson/Jenkins) > > yet, but I have never looked actively for something like that. > > > > Publishing a build via Dropbox sounds somehow strange, but maybe the > > right solution for those playing Rails via Dropbox anyway. However I do > > not volunteer to providing such a solution. > > But maybe a more frequent publication of bug-fix releases will be a > > solution, but possibly I should not to give too much promises before I > > really know how difficult it will be to get the built up to Sourceforge. > > > > Stefan > > --------------------------------------------------------------------------- > --- All the data continuously generated in your IT infrastructure contains > a definitive record of customers, application performance, security > threats, fraudulent activity and more. Splunk takes this data and makes > sense of it. Business sense. IT sense. Common sense. > http://p.sf.net/sfu/splunk-d2dcopy1 > _______________________________________________ > Rails-devel mailing list > Rai...@li... > https://lists.sourceforge.net/lists/listinfo/rails-devel |
|
From: brett l. <bre...@gm...> - 2011-09-22 17:35:41
|
Mike - I appreciate the suggestion, but a Dropbox folder is not an appropriate location for nightly builds. I don't want to confuse people by requiring them to got to different locations to find different copies of our work. Sourceforge gives us some shell space that might be able to host a script to generate nightly builds that are then posted to http://rails.sf.net and hosted by Sourceforge. Though, honestly with the low level of activity, we could probably be fine with weekly builds. You've been a semi-regular contributor for a while now, I'd be open to providing you with sufficient access to the sourceforge resources to allow you to set this up. ---Brett. 2011/9/22 Michał Bażyński <ba...@tl...>: > > I could take on the task of providing nightly builds in between releases > in a public dropbox folder. > I thought a sourceforge site was a better place for it so didn't > volunteer, but if this being served on dropbox and not sourceforge I can > do it. (I am assuming only patches that have bug fixes would be served > publicly, not newly developed stuff). > > as to your change log for the next release why not mention 1830 wabash > is now working? if someone tried playing that and gave up he might be > interested it is now working... > > mike > > On 11-09-22 18:32, Stefan Frey wrote: >> Chris: >> as already stated I like the idea of more frequent builds. However for nightly >> builds I would prefer an automated setup: To my knowledge there is no public >> build server for java projects (e.g. using Hudson/Jenkins) yet, but I have >> never looked actively for something like that. >> >> Publishing a build via Dropbox sounds somehow strange, but maybe the right >> solution for those playing Rails via Dropbox anyway. However I do not >> volunteer to providing such a solution. >> But maybe a more frequent publication of bug-fix releases will be a solution, >> but possibly I should not to give too much promises before I really know how >> difficult it will be to get the built up to Sourceforge. >> >> Stefan > > |
|
From: Michał B. <ba...@tl...> - 2011-09-22 18:49:49
|
if sourceforge allows running bash scripts from a cron on a machine that can git pull and ant and scp to the file server it should be pretty trivial to write it. I'll play with it on my own when I get an hour or two (it's been a while since I did stuff like this). I'll let you know when I feel I can have it set up reasonably quickly. (and yes, I think sourceforge is a LOT better place for hosting this than dropbox). On 11-09-22 19:35, brett lentz wrote: > Mike - > > I appreciate the suggestion, but a Dropbox folder is not an > appropriate location for nightly builds. I don't want to confuse > people by requiring them to got to different locations to find > different copies of our work. > > Sourceforge gives us some shell space that might be able to host a > script to generate nightly builds that are then posted to > http://rails.sf.net and hosted by Sourceforge. Though, honestly with > the low level of activity, we could probably be fine with weekly > builds. > > You've been a semi-regular contributor for a while now, I'd be open to > providing you with sufficient access to the sourceforge resources to > allow you to set this up. > > ---Brett. > > > > 2011/9/22 Michał Bażyński<ba...@tl...>: >> I could take on the task of providing nightly builds in between releases >> in a public dropbox folder. >> I thought a sourceforge site was a better place for it so didn't >> volunteer, but if this being served on dropbox and not sourceforge I can >> do it. (I am assuming only patches that have bug fixes would be served >> publicly, not newly developed stuff). >> >> as to your change log for the next release why not mention 1830 wabash >> is now working? if someone tried playing that and gave up he might be >> interested it is now working... >> >> mike >> >> On 11-09-22 18:32, Stefan Frey wrote: >>> Chris: >>> as already stated I like the idea of more frequent builds. However for nightly >>> builds I would prefer an automated setup: To my knowledge there is no public >>> build server for java projects (e.g. using Hudson/Jenkins) yet, but I have >>> never looked actively for something like that. >>> >>> Publishing a build via Dropbox sounds somehow strange, but maybe the right >>> solution for those playing Rails via Dropbox anyway. However I do not >>> volunteer to providing such a solution. >>> But maybe a more frequent publication of bug-fix releases will be a solution, >>> but possibly I should not to give too much promises before I really know how >>> difficult it will be to get the built up to Sourceforge. >>> >>> Stefan >> > ------------------------------------------------------------------------------ > All the data continuously generated in your IT infrastructure contains a > definitive record of customers, application performance, security > threats, fraudulent activity and more. Splunk takes this data and makes > sense of it. Business sense. IT sense. Common sense. > http://p.sf.net/sfu/splunk-d2dcopy1 > _______________________________________________ > Rails-devel mailing list > Rai...@li... > https://lists.sourceforge.net/lists/listinfo/rails-devel |
|
From: Erik V. <eri...@xs...> - 2011-09-22 16:19:06
|
This inspired me to update the change log, which I had ignored for the last 9 weeks (partly because someone deemed it superfluous). It's not as detailed as you would find in the Git history, but for the final (post-release) version it will need to be reformatted and further summarized (as Brett and I have done for past releases). Erik. > -----Original Message----- > From: Stefan Frey [mailto:ste...@we...] > Sent: Thursday, September 22, 2011 2:23 PM > To: Development list for Rails: an 18xx game > Subject: [Rails-devel] New release coming out tonight > > All: > Brett gave me the permissions, so I will publish a new release 1.5 today. > > It seems that the main features are: > > * 18GA complete > * 18TN complete > * Full support for 1830 Coalfield rights and revenue calculation > > Anything to add there? > > For a complete list of changes and bug fixes I will refer to the wiki page. > > I intend to make bug fix releases in the future (with version numbers 1.x.y) > which are published more frequently than the previous 1.x releases. > > Stefan > > ---------------------------------------------------------------------------- -- > All the data continuously generated in your IT infrastructure contains a > definitive record of customers, application performance, security threats, > fraudulent activity and more. Splunk takes this data and makes sense of it. > Business sense. IT sense. Common sense. > http://p.sf.net/sfu/splunk-d2dcopy1 > _______________________________________________ > Rails-devel mailing list > Rai...@li... > https://lists.sourceforge.net/lists/listinfo/rails-devel |
|
From: Stefan F. <ste...@we...> - 2011-09-22 16:23:39
|
Erik: The llst below was intended as the beginning of such a summary: * 18GA complete * 18TN complete * Full support for 1830 Coalfield rights and revenue calculation Feel free to add. I will send out the release note tomorrow morning (European time), thus anything submitted before this deadline will be added. Stefan On Thursday, September 22, 2011 06:18:55 pm Erik Vos wrote: > This inspired me to update the change log, which I had ignored for the last > 9 weeks (partly because someone deemed it superfluous). > It's not as detailed as you would find in the Git history, but for the > final (post-release) version it will need to be reformatted and further > summarized (as Brett and I have done for past releases). > > Erik. > > > -----Original Message----- > > From: Stefan Frey [mailto:ste...@we...] > > Sent: Thursday, September 22, 2011 2:23 PM > > To: Development list for Rails: an 18xx game > > Subject: [Rails-devel] New release coming out tonight > > > > All: > > Brett gave me the permissions, so I will publish a new release 1.5 today. > > > > It seems that the main features are: > > > > > > Anything to add there? > > > > For a complete list of changes and bug fixes I will refer to the wiki > > page. > > > I intend to make bug fix releases in the future (with version numbers > > 1.x.y) > > > which are published more frequently than the previous 1.x releases. > > > > Stefan > > --------------------------------------------------------------------------- > - -- > > > All the data continuously generated in your IT infrastructure contains a > > definitive record of customers, application performance, security > > threats, fraudulent activity and more. Splunk takes this data and makes > > sense of > > it. > > > Business sense. IT sense. Common sense. > > http://p.sf.net/sfu/splunk-d2dcopy1 > > _______________________________________________ > > Rails-devel mailing list > > Rai...@li... > > https://lists.sourceforge.net/lists/listinfo/rails-devel > > --------------------------------------------------------------------------- > --- All the data continuously generated in your IT infrastructure contains > a definitive record of customers, application performance, security > threats, fraudulent activity and more. Splunk takes this data and makes > sense of it. Business sense. IT sense. Common sense. > http://p.sf.net/sfu/splunk-d2dcopy1 > _______________________________________________ > Rails-devel mailing list > Rai...@li... > https://lists.sourceforge.net/lists/listinfo/rails-devel |
|
From: Michał B. <ba...@tl...> - 2011-09-22 16:28:43
Attachments:
0001-in-1830-wabash-7Ts-rust-4Ts.patch
|
a patch fixing wabash 1830 variant. 7Ts should rust 4Ts. |
|
From: Stefan F. <ste...@we...> - 2011-09-22 16:39:33
|
Mike, patch applied. Could you provide a save file with a test case, I would like to add that to the test suite. Thanks, Stefan On Thursday, September 22, 2011 06:29:04 pm Michał Bażyński wrote: > a patch fixing wabash 1830 variant. > > 7Ts should rust 4Ts. |
|
From: Michał B. <ba...@tl...> - 2011-09-22 16:46:20
|
what makes a testcase? a save file with my text description what should be done, or a java class that loads the save, does a train purchase operation and checks if the 4s died? if it's the latter it might take some time, everytime I try to navigate your java code my brain melts, it's been a LOOONG time since I've sent you a NullPointerException fix... On 11-09-22 18:42, Stefan Frey wrote: > Mike, > patch applied. > Could you provide a save file with a test case, I would like to add that to > the test suite. > > Thanks, > Stefan > > > On Thursday, September 22, 2011 06:29:04 pm Michał Bażyński wrote: >> a patch fixing wabash 1830 variant. >> >> 7Ts should rust 4Ts. > ------------------------------------------------------------------------------ > All the data continuously generated in your IT infrastructure contains a > definitive record of customers, application performance, security > threats, fraudulent activity and more. Splunk takes this data and makes > sense of it. Business sense. IT sense. Common sense. > http://p.sf.net/sfu/splunk-d2dcopy1 > _______________________________________________ > Rails-devel mailing list > Rai...@li... > https://lists.sourceforge.net/lists/listinfo/rails-devel |
|
From: Stefan F. <ste...@we...> - 2011-09-22 16:55:04
|
The code to load a save file and check if that still does what it previously did is already written (see classes in test package: TestGameBuilder and TestGame). To run all test games simply run the TestGameBuilder as JUnit test. This reminds me to add more text about this to the according wiki page. So the save file of the test game (at either the end of game or at least after the purchase of 7-train is enough). And this is again a request to submit finished games of the new games and variants which are not yet tested automatically. See current list of test cases in the wiki: http://sourceforge.net/apps/mediawiki/rails/index.php?title=Automated_game_testing On Thursday, September 22, 2011 06:46:42 pm Michał Bażyński wrote: > what makes a testcase? a save file with my text description what should > be done, or a java class that loads the save, does a train purchase > operation and checks if the 4s died? if it's the latter it might take > some time, everytime I try to navigate your java code my brain melts, > it's been a LOOONG time since I've sent you a NullPointerException fix... > > On 11-09-22 18:42, Stefan Frey wrote: > > Mike, > > patch applied. > > Could you provide a save file with a test case, I would like to add that > > to the test suite. > > > > Thanks, > > Stefan > > > > On Thursday, September 22, 2011 06:29:04 pm Michał Bażyński wrote: > >> a patch fixing wabash 1830 variant. > >> > >> 7Ts should rust 4Ts. > > > > ------------------------------------------------------------------------- > > ----- All the data continuously generated in your IT infrastructure > > contains a definitive record of customers, application performance, > > security threats, fraudulent activity and more. Splunk takes this data > > and makes sense of it. Business sense. IT sense. Common sense. > > http://p.sf.net/sfu/splunk-d2dcopy1 > > _______________________________________________ > > Rails-devel mailing list > > Rai...@li... > > https://lists.sourceforge.net/lists/listinfo/rails-devel > > --------------------------------------------------------------------------- > --- All the data continuously generated in your IT infrastructure contains > a definitive record of customers, application performance, security > threats, fraudulent activity and more. Splunk takes this data and makes > sense of it. Business sense. IT sense. Common sense. > http://p.sf.net/sfu/splunk-d2dcopy1 > _______________________________________________ > Rails-devel mailing list > Rai...@li... > https://lists.sourceforge.net/lists/listinfo/rails-devel |
|
From: Michał B. <ba...@tl...> - 2011-09-22 16:55:56
|
in a true continous integration evironment the nightly build does mean something different, but a true nightly build has no reason being publicly distributed in this case I think. the problem is the wait before a bugfix being commited, and a minor release with the fix being available. if you intend to release all the bug fix commits as they are made, there's no need for anything more I think. but in the case of delays like the one happening right now with 1.4.2 being quite buggy I could be serving players the fixes sooner. On 11-09-22 18:45, Stefan Frey wrote: > In my understanding the inclusion of new stuff is the defining difference > between nightly builds and bug-fix releases to the latest stable release, but > opinions might differ here. > > And I would try for a bug fix release only to apply those changes to the > latest stable release which are clear fixes and not new features etc. > > This is something that the change to git makes much easier to accomplish. > > Stefan > > On Thursday, September 22, 2011 06:36:32 pm Michał Bażyński wrote: >> I could take on the task of providing nightly builds in between releases >> in a public dropbox folder. >> I thought a sourceforge site was a better place for it so didn't >> volunteer, but if this being served on dropbox and not sourceforge I can >> do it. (I am assuming only patches that have bug fixes would be served >> publicly, not newly developed stuff). >> >> as to your change log for the next release why not mention 1830 wabash >> is now working? if someone tried playing that and gave up he might be >> interested it is now working... >> >> mike |
|
From: Charles S. <men...@gm...> - 2011-09-22 18:06:14
|
Is this going to include all the latest bug fixes, e.g., 1830 wabash, etc.? 2011/9/22 Michał Bażyński <ba...@tl...> > > in a true continous integration evironment the nightly build does mean > something different, but a true nightly build has no reason being > publicly distributed in this case I think. the problem is the wait > before a bugfix being commited, and a minor release with the fix being > available. if you intend to release all the bug fix commits as they are > made, there's no need for anything more I think. but in the case of > delays like the one happening right now with 1.4.2 being quite buggy I > could be serving players the fixes sooner. > > On 11-09-22 18:45, Stefan Frey wrote: > > In my understanding the inclusion of new stuff is the defining difference > > between nightly builds and bug-fix releases to the latest stable release, > but > > opinions might differ here. > > > > And I would try for a bug fix release only to apply those changes to the > > latest stable release which are clear fixes and not new features etc. > > > > This is something that the change to git makes much easier to accomplish. > > > > Stefan > > > > On Thursday, September 22, 2011 06:36:32 pm Michał Bażyński wrote: > >> I could take on the task of providing nightly builds in between releases > >> in a public dropbox folder. > >> I thought a sourceforge site was a better place for it so didn't > >> volunteer, but if this being served on dropbox and not sourceforge I can > >> do it. (I am assuming only patches that have bug fixes would be served > >> publicly, not newly developed stuff). > >> > >> as to your change log for the next release why not mention 1830 wabash > >> is now working? if someone tried playing that and gave up he might be > >> interested it is now working... > >> > >> mike > > > > ------------------------------------------------------------------------------ > All the data continuously generated in your IT infrastructure contains a > definitive record of customers, application performance, security > threats, fraudulent activity and more. Splunk takes this data and makes > sense of it. Business sense. IT sense. Common sense. > http://p.sf.net/sfu/splunk-d2dcopy1 > _______________________________________________ > Rails-devel mailing list > Rai...@li... > https://lists.sourceforge.net/lists/listinfo/rails-devel > |
|
From: Chris S. <chr...@gm...> - 2011-09-22 18:24:38
|
I don't really care where it happens, I just would like to see something that allows non-technical players to get a copy of the bug fixes so their games aren't on hold for weeks at a time waiting for a new release. -- Chris Please consider the environment before printing this e-mail. On Thu, Sep 22, 2011 at 10:35 AM, brett lentz <bre...@gm...> wrote: > Mike - > > I appreciate the suggestion, but a Dropbox folder is not an > appropriate location for nightly builds. I don't want to confuse > people by requiring them to got to different locations to find > different copies of our work. > > Sourceforge gives us some shell space that might be able to host a > script to generate nightly builds that are then posted to > http://rails.sf.net and hosted by Sourceforge. Though, honestly with > the low level of activity, we could probably be fine with weekly > builds. > > You've been a semi-regular contributor for a while now, I'd be open to > providing you with sufficient access to the sourceforge resources to > allow you to set this up. > > ---Brett. > > > > 2011/9/22 Michał Bażyński <ba...@tl...>: >> >> I could take on the task of providing nightly builds in between releases >> in a public dropbox folder. >> I thought a sourceforge site was a better place for it so didn't >> volunteer, but if this being served on dropbox and not sourceforge I can >> do it. (I am assuming only patches that have bug fixes would be served >> publicly, not newly developed stuff). >> >> as to your change log for the next release why not mention 1830 wabash >> is now working? if someone tried playing that and gave up he might be >> interested it is now working... >> >> mike >> >> On 11-09-22 18:32, Stefan Frey wrote: >>> Chris: >>> as already stated I like the idea of more frequent builds. However for nightly >>> builds I would prefer an automated setup: To my knowledge there is no public >>> build server for java projects (e.g. using Hudson/Jenkins) yet, but I have >>> never looked actively for something like that. >>> >>> Publishing a build via Dropbox sounds somehow strange, but maybe the right >>> solution for those playing Rails via Dropbox anyway. However I do not >>> volunteer to providing such a solution. >>> But maybe a more frequent publication of bug-fix releases will be a solution, >>> but possibly I should not to give too much promises before I really know how >>> difficult it will be to get the built up to Sourceforge. >>> >>> Stefan >> >> > > ------------------------------------------------------------------------------ > All the data continuously generated in your IT infrastructure contains a > definitive record of customers, application performance, security > threats, fraudulent activity and more. Splunk takes this data and makes > sense of it. Business sense. IT sense. Common sense. > http://p.sf.net/sfu/splunk-d2dcopy1 > _______________________________________________ > Rails-devel mailing list > Rai...@li... > https://lists.sourceforge.net/lists/listinfo/rails-devel > |
|
From: brett l. <bre...@gm...> - 2011-09-22 18:40:47
|
I understand, and apologize for the frustration our release delays have caused. This time around, the situation was somewhat unique. I don't plan on moving cross-country again. (at least, not for quite a while) ;-) I've also taken steps to ensure that at least two people have access to all parts of the project. The project has grown to the point where it truly is a community effort. So, I am now no longer the sole keeper of any part of the project. This should help avoid any single person's absence from the project preventing the project from moving forward, including my own. With that said, I've been involved to varying degrees in open source projects for the last 12-13 years or so. One of the worst things that far too many projects do, is fragmenting themselves across multiple web and service providers. This provides an inconsistent and often sub-par experience to users of the project. We're a small enough project as-is. I want to make sure that downloading our code and our packaged app is as easy as possible, especially for our less technically savvy users. I'm totally on board with providing automated nightly builds. I think it's a great idea, and one I've had myself. However, I want to put those builds in a place users already know about. This assures that they'll be easy to find and easy to obtain for anyone. ---Brett. On Thu, Sep 22, 2011 at 2:24 PM, Chris Shaffer <chr...@gm...> wrote: > I don't really care where it happens, I just would like to see > something that allows non-technical players to get a copy of the bug > fixes so their games aren't on hold for weeks at a time waiting for a > new release. > > -- > Chris > > Please consider the environment before printing this e-mail. > > > > On Thu, Sep 22, 2011 at 10:35 AM, brett lentz <bre...@gm...> wrote: >> Mike - >> >> I appreciate the suggestion, but a Dropbox folder is not an >> appropriate location for nightly builds. I don't want to confuse >> people by requiring them to got to different locations to find >> different copies of our work. >> >> Sourceforge gives us some shell space that might be able to host a >> script to generate nightly builds that are then posted to >> http://rails.sf.net and hosted by Sourceforge. Though, honestly with >> the low level of activity, we could probably be fine with weekly >> builds. >> >> You've been a semi-regular contributor for a while now, I'd be open to >> providing you with sufficient access to the sourceforge resources to >> allow you to set this up. >> >> ---Brett. >> >> >> >> 2011/9/22 Michał Bażyński <ba...@tl...>: >>> >>> I could take on the task of providing nightly builds in between releases >>> in a public dropbox folder. >>> I thought a sourceforge site was a better place for it so didn't >>> volunteer, but if this being served on dropbox and not sourceforge I can >>> do it. (I am assuming only patches that have bug fixes would be served >>> publicly, not newly developed stuff). >>> >>> as to your change log for the next release why not mention 1830 wabash >>> is now working? if someone tried playing that and gave up he might be >>> interested it is now working... >>> >>> mike >>> >>> On 11-09-22 18:32, Stefan Frey wrote: >>>> Chris: >>>> as already stated I like the idea of more frequent builds. However for nightly >>>> builds I would prefer an automated setup: To my knowledge there is no public >>>> build server for java projects (e.g. using Hudson/Jenkins) yet, but I have >>>> never looked actively for something like that. >>>> >>>> Publishing a build via Dropbox sounds somehow strange, but maybe the right >>>> solution for those playing Rails via Dropbox anyway. However I do not >>>> volunteer to providing such a solution. >>>> But maybe a more frequent publication of bug-fix releases will be a solution, >>>> but possibly I should not to give too much promises before I really know how >>>> difficult it will be to get the built up to Sourceforge. >>>> >>>> Stefan >>> >>> >> >> ------------------------------------------------------------------------------ >> All the data continuously generated in your IT infrastructure contains a >> definitive record of customers, application performance, security >> threats, fraudulent activity and more. Splunk takes this data and makes >> sense of it. Business sense. IT sense. Common sense. >> http://p.sf.net/sfu/splunk-d2dcopy1 >> _______________________________________________ >> Rails-devel mailing list >> Rai...@li... >> https://lists.sourceforge.net/lists/listinfo/rails-devel >> > > ------------------------------------------------------------------------------ > All the data continuously generated in your IT infrastructure contains a > definitive record of customers, application performance, security > threats, fraudulent activity and more. Splunk takes this data and makes > sense of it. Business sense. IT sense. Common sense. > http://p.sf.net/sfu/splunk-d2dcopy1 > _______________________________________________ > Rails-devel mailing list > Rai...@li... > https://lists.sourceforge.net/lists/listinfo/rails-devel > |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X