We don't get payed but it's still good to have some commitment. Even if
we do this for ourselves.
I set release date for Windsor/Core/DynamicProxy to 6 months from now
(2nd/3rd quarter)
for a minor version mostly to provide binaries for .NET 4.0 with some
4.0 functionality.
I know that the thread about Windsor has lots of ideas (many breaking)
that would require
a major release, but I don't think we'll be able to get this ready
within 6 months, so I would like
to have a minor version Windsor 2.2 done 6 months from now, and v3.0 6
months after that.
Having a consistent release schedule is crucial, and it would be great
if we could align all projects
(especially major ones) to coincide with major releases (so that we'd
have MonoRail 3.0 and
ActiveRecord 3.0 released within a year) plus each project would release
its minor versions
during the year according to its own schedule. The only impact that
would have on projects depending
on it, would be that they would have to have a point point one release,
with updated references
and perhaps some bugs fixed ported from the trunk to last major release'
branch.
Krzysztof
On 2010-01-23 08:38, Ken Egozi wrote:
Hmm. I think I can hear Hammet's thoughts now:
"clients? I don't remember getting paid by anyone for that"
:)
On Sat, Jan 23, 2010 at 6:40 AM, John Simons
<[email protected] <mailto:[email protected]>> wrote:
Henry,
I tend to disagree with that, in my opinion it's worse to lose a
prospect client because we do not show commitment, then state the
reason for why the release is being delayed.
A good case of that is VS2010, MS has delayed it's release, and
provided us with good reasons why.
I didn't say that we have to commit to a set in stone release date, we
all know that is very hard to do, but if we keep the release dates up
to date and even if we change them we communicate the reason why it
has to delayed or brought forward, I think that is good client
interaction.
Cheers
John
On Jan 23, 3:21 pm, Henry Conceição <[email protected]
<mailto:[email protected]>> wrote:
> If we set a deadline and don't meet her, it'll be worst, since we'll
> be disappointing the users and ourselves.
>
> And people can feel cheated by a release date that always is
pushed to
> some point in the future. If we had set a date for Monorail
after the
> last RC, probably we would be know by the Duke Nuke Forever of the
> .Net plataform.
>
> Cheers,
> Henry Conceição
>
> On Sat, Jan 23, 2010 at 1:27 AM, John Simons
<[email protected] <mailto:[email protected]>>
wrote:
> > I'm afraid that TBD is still very infinite.
>
> > Cheers
> > John
>
> > On Jan 23, 2:18 pm, Henry Conceição <[email protected]
<mailto:[email protected]>> wrote:
> >> Yeah, I had the same feeling. So i changed the major projects
fpr TBD
> >> instead none planning earlier today.
>
> >> Cheers,
> >> Henry Conceição
>
> >> On Fri, Jan 22, 2010 at 11:39 PM, John Simons
>
> >> <[email protected]
<mailto:[email protected]>> wrote:
> >> > I have been on a course for the last week and I got some
feedback from
> >> > one of the attendees about the term we use on the projects
web page
> >> > (http://www.castleproject.org/castle/projects.html) - "None
> >> > planned".
>
> >> > His advice was that if we say "None planned" it feels like
the project
> >> > is not active!
> >> > So, I was thinking of changing it to be something a bit more
> >> > optimistic, such as "Coming soon" or "TBA", but all these
terms are
> >> > very indefinite, so I actually think we should use terms
like "First
> >> > quarter of 2010" or "March 2010".
>
> >> > Thoughts?
>
> >> > Cheers
> >> > John
>
> >> > --
> >> > You received this message because you are subscribed to the
Google Groups "Castle Project Development List" group.
> >> > To post to this group, send email to
[email protected]
<mailto:[email protected]>.
> >> > To unsubscribe from this group, send email to
[email protected]
<mailto:castle-project-devel%[email protected]>.
> >> > For more options, visit this group
athttp://groups.google.com/group/castle-project-devel?hl=en
<http://groups.google.com/group/castle-project-devel?hl=en>.
>
> > --
> > You received this message because you are subscribed to the
Google Groups "Castle Project Development List" group.
> > To post to this group, send email to
[email protected]
<mailto:[email protected]>.
> > To unsubscribe from this group, send email to
[email protected]
<mailto:castle-project-devel%[email protected]>.
> > For more options, visit this group
athttp://groups.google.com/group/castle-project-devel?hl=en
<http://groups.google.com/group/castle-project-devel?hl=en>.
--
You received this message because you are subscribed to the Google
Groups "Castle Project Development List" group.
To post to this group, send email to
[email protected]
<mailto:[email protected]>.
To unsubscribe from this group, send email to
[email protected]
<mailto:castle-project-devel%[email protected]>.
For more options, visit this group at
http://groups.google.com/group/castle-project-devel?hl=en.
--
Ken Egozi.
http://www.kenegozi.com/blog
http://www.delver.com
http://www.musicglue.com
http://www.castleproject.org
http://www.idcc.co.il - הכנס הקהילתי הראשון למפתחי דוטנט - בואו בהמוניכם
--
You received this message because you are subscribed to the Google
Groups "Castle Project Development List" group.
To post to this group, send email to
[email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/castle-project-devel?hl=en.
--
You received this message because you are subscribed to the Google Groups "Castle
Project Development List" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/castle-project-devel?hl=en.
