RE: [Slashcode-development] release plan

[<Vl...@ge...>]

August?!  The problem I see with that (as someone on the outside looking in)
is the upgrade stuff.  Not only is that a short period of time to declare a
feature freeze, fix all outstanding bugs, and what not, but the upgrade
stuff isn't ready yet from what I understand.  Sure, it would be nice to
have a 2.2.7, or a 2.4.0, but at the rate slash is evolving, it might be
more like 3.0 in December or next year.  The T_ and R_ tags are, IM(NS)HO
annoying, sure.  But, with tallented people like you submitting patches, and
the team cranking out code on this, I think we can put up with it a while
longer.  :-)

Scott

--

 /"\                         / For information and quotes, email us at
 \ /  ASCII RIBBON CAMPAIGN / in...@lr...
  X   AGAINST HTML MAIL    / http://www.lrsehosting.com/
 / \  AND POSTINGS        / vl...@lr...
-------------------------------------------------------------------------

> -----Original Message-----
> From: sla...@li...
> [mailto:sla...@li...]On Behalf Of
> shane
> Sent: Friday, June 20, 2003 7:24 AM
> To: sla...@li...
> Subject: [Slashcode-development] release plan
>
>
> What's OSDN's plans for releasing Slash?
>
> Will we ever see a 2.2.7 or 2.3?
>
> Is the plan to 'go by cvs' for the forseeable future?
>
> I ask because it is extremely hard to tell people, that
> inorder to use a
> plugin, they need to be using CVS. Is that CVS from this
> morning? yesterday?
> 5 days ago? 3 months?
>
> Yes, I understand about T_ tags, and R_tags. I've used both.
> The point I want
> to make is that with 'going by cvs' seemingly being the way
> it'll be for a
> while, it makes it really hard to release a plugin that is
> compatible with
> current slash - unless you go by 2.2.6 or a T or R tag. (and
> people don't
> always seem to understand the tagging, and/or take the time
> to read the
> information that's out there about how t_ and r_ tags are used).
>
> Personally, it would be far easier for me if it were decided,
> and released,
> that the next version will be 2.2.7 and you'll try to put it
> out in august.
> Atleast that way we can release code that's compatible with
> it. Releasing
> code that works with 2.2.6... well, that's almost over a year old now.
>
> I don't want to rile any feathers, just find out what the
> plan of attack is.
>
> Thanks,
>  Shane
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by: INetU
> Attention Web Developers & Consultants: Become An INetU
> Hosting Partner.
> Refer Dedicated Servers. We Manage Them. You Get 10% Monthly
> Commission!
> INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php
> _______________________________________________
> Slashcode-development mailing list
> Sla...@li...
> https://lists.sourceforge.net/lists/listinfo/slashcode-development
>