From: Michael J. <mi...@fi...> - 2002-09-12 18:27:08
|
So, it's been a bit quiet here. I don't think I need to be guilty in asking a more general question about the direction of Slash. What is slated for the next major release of Slash? Is there a link on the website about this? just curious. -mj |
From: Rob 'C. M. <ma...@sl...> - 2002-09-12 19:07:49
|
I don't think any of us have stated any such thing. I think that when Zoo2 settles down, I'd like to formally do another release tho... just MHO. On Thursday 12 September 2002 02:27 pm, Michael Johnson wrote: > So, it's been a bit quiet here. I don't think I need to be guilty in > asking a more general question about the direction of Slash. > > What is slated for the next major release of Slash? Is there a link on the > website about this? > > just curious. > > -mj > > > > ------------------------------------------------------- > This sf.net email is sponsored by:ThinkGeek > Welcome to geek heaven. > http://thinkgeek.com/sf > _______________________________________________ > Slashcode-general mailing list > Sla...@li... > https://lists.sourceforge.net/lists/listinfo/slashcode-general |
From: Michael J. <mi...@fi...> - 2002-09-12 19:22:53
|
I never actually said you _had_ "stated any such thing." :-) I was _asking_ if there was any writeup in respect to work items planned for future releases in respect to the Slash code. In the event that there is no writeup, I was hoping someone could inform me (however informally) of what might be pending in the next release, if there is going to be one. That said, I think you've answered my question, however oddly. Now, although I may have already made myself sound like a complete moron, I believe "in for a penny...." What the heck is Zoo2? -mj On Thu, 12 Sep 2002, Rob 'CmdrTaco' Malda wrote: > I don't think any of us have stated any such thing. > > I think that when Zoo2 settles down, I'd like to formally do another release > tho... just MHO. > > > On Thursday 12 September 2002 02:27 pm, Michael Johnson wrote: > > So, it's been a bit quiet here. I don't think I need to be guilty in > > asking a more general question about the direction of Slash. > > > > What is slated for the next major release of Slash? Is there a link on the > > website about this? > > > > just curious. > > > > -mj > > > > > > > > ------------------------------------------------------- > > This sf.net email is sponsored by:ThinkGeek > > Welcome to geek heaven. > > http://thinkgeek.com/sf > > _______________________________________________ > > Slashcode-general mailing list > > Sla...@li... > > https://lists.sourceforge.net/lists/listinfo/slashcode-general > |
From: Brian A. <br...@ta...> - 2002-09-12 19:28:15
|
On Thu, 2002-09-12 at 12:22, Michael Johnson wrote: > I never actually said you _had_ "stated any such thing." :-) I was > _asking_ if there was any writeup in respect to work items planned for > future releases in respect to the Slash code. In the event that there is > no writeup, I was hoping someone could inform me (however informally) of > what might be pending in the next release, if there is going to be one. > That said, I think you've answered my question, however oddly. Personally I think tarball releases (unless they come from CVS) are not the greatest thing. I would rather see a rolling release using CVS and its tags. Upgrading from CVS is safe (assuming you use the tags we use for Slashdot) and you are far more likely to get current code this way. I do this with my sites and it works quite well. -Brian -- _______________________________________________________ Brian "Krow" Aker, br...@ta... Slashdot Senior Developer Seattle, Washington http://krow.net/ http://askbrian.org/ _______________________________________________________ You can't grep a dead tree. |
From: Michael J. <mi...@fi...> - 2002-09-12 19:39:07
|
On 12 Sep 2002, Brian Aker wrote: > Personally I think tarball releases (unless they come from CVS) are not > the greatest thing. I would rather see a rolling release using CVS and > its tags. > > Upgrading from CVS is safe (assuming you use the tags we use for > Slashdot) and you are far more likely to get current code this way. I do > this with my sites and it works quite well. > > -Brian Yeh, that makes sense. I guess you could just use branching and just document which branch to use for what---the official version and the version in development....sort of like BSD* does. Of course, you could monitor what is happening and changing with the slash package via CVS as well, but it doesn't show a planned development path officially if there is one. I was just kind of wondering what the development picture was like etc. for the future, if there is one. I don't think using CVS and branching would clarify this, unless this was included in the docs somehow under TODO or something. I don't think I'm communicating very clearly. -mj |
From: i18n <i1...@ya...> - 2002-09-12 19:47:48
|
At 12:39 PM 9/12/2002 -0700, Michael Johnson wrote: >I don't think I'm communicating very clearly. I think what Michael is asking is: "Is there a plan, grand or otherwise, about what features to expect in future releases, especially those release not in the immediate near future. this doesn't have to be carved in stone, I just want to get an idea (and I might be willing to help with some of the coding). Usually projects refer to what I am asking about as the 'roadmap' if that helps...." But then again I am just putting words in his mouth.... Barry |
From: Michael J. <mi...@fi...> - 2002-09-12 19:52:48
|
On Thu, 12 Sep 2002, i18n wrote: > At 12:39 PM 9/12/2002 -0700, Michael Johnson wrote: > >I don't think I'm communicating very clearly. > > > I think what Michael is asking is: > > "Is there a plan, grand or otherwise, about what features to expect in future releases, especially those release not in the immediate near future. this doesn't have to be carved in stone, I just want to get an idea (and I might be willing to help with some of the coding). Usually projects refer to what I am asking about as the 'roadmap' if that helps...." > > But then again I am just putting words in his mouth.... Not really. You are correct. That is what I was trying to ask. -mj |
From: Michael J. <mi...@fi...> - 2002-09-12 19:53:50
|
On Thu, 12 Sep 2002, i18n wrote: > At 12:39 PM 9/12/2002 -0700, Michael Johnson wrote: > >I don't think I'm communicating very clearly. > > > I think what Michael is asking is: > > "Is there a plan, grand or otherwise, about what features to expect in future releases, especially those release not in the immediate near future. this doesn't have to be carved in stone, I just want to get an idea (and I might be willing to help with some of the coding). Usually projects refer to what I am asking about as the 'roadmap' if that helps...." > > But then again I am just putting words in his mouth.... Not really. You are correct. That is what I was trying to ask. -mj |
From: Brian A. <br...@ta...> - 2002-09-12 20:25:18
|
On Thu, 2002-09-12 at 12:39, Michael Johnson wrote: > Yeh, that makes sense. I guess you could just use branching and just > document which branch to use for what---the official version and the > version in development....sort of like BSD* does. Something like that. > Of course, you could monitor what is happening and changing with the slash > package via CVS as well, but it doesn't show a planned development path > officially if there is one. I was just kind of wondering what the > development picture was like etc. for the future, if there is one. I don't The answer is that the newer stuff to be added really hasn't been decided on and it is coming down to what sites need at the moment. Slashdot needs Zoo so I am working on Zoo. Others have pretty similar tasks at the moment. The big stuff is in place, its more about improving on what we have at the moment. You can expect to see more enhancements to search in the near future and adminmail is being improved upon. Upgrading right now is grabbing CVS, make install, run the right commands from updates (and I am looking at lifting Livejournal's SQL update code since it is the best I have seen). Something to scan plugins/themes for new tasks would be nice but I don't have the time to do it. It would also be nice to have a way to generate a THEME from an existing site. This is the sort of script that I think someone in the community ought to look into doing. It is mainly a matter of scanning the site_info table and comparing templates (the code exists in Slash::Install to do this). -Brian -- _______________________________________________________ Brian "Krow" Aker, br...@ta... Slashdot Senior Developer Seattle, Washington http://krow.net/ http://askbrian.org/ _______________________________________________________ You can't grep a dead tree. |
From: Alessio B. <al...@al...> - 2002-09-17 06:47:15
|
On Thu, 2002-09-12 at 22:22, Brian Aker wrote: > Upgrading from CVS is safe (assuming you use the tags we use for > Slashdot) and you are far more likely to get current code this way. I do > this with my sites and it works quite well. But it makes really difficult to follow developments for site which don't want or cannot spend a lot of time micro-upgrading every week. And I have an extra problem: I maintain a Slash translation in Italian and I cannot really merge my CVS and main CVS without a fixed point in development. That's why in a previous discussion I've asked not to focus only on CVS updates but to do proper releases from time to time. -- Alessio F. Bragadini al...@al... APL Financial Services http://village.albourne.com Nicosia, Cyprus phone: +357-22-755750 "It is more complicated than you think" -- The Eighth Networking Truth from RFC 1925 |