Hi Luc.
> > I have to agree with James here. However, if the mysterious
> > team-who-wishes-to-contribute is dead set on 6 month release cycles,
> > it is certainly within their power to make sure 4.5 months ahead of
> > time that every open JIRA issue has a patch attached, and to nag the
> > tea
Hi,
Le 27/03/2012 21:08, Matt Benson a écrit :
> I have to agree with James here. However, if the mysterious
> team-who-wishes-to-contribute is dead set on 6 month release cycles,
> it is certainly within their power to make sure 4.5 months ahead of
> time that every open JIRA issue has a patch a
I have to agree with James here. However, if the mysterious
team-who-wishes-to-contribute is dead set on 6 month release cycles,
it is certainly within their power to make sure 4.5 months ahead of
time that every open JIRA issue has a patch attached, and to nag the
team incessantly for the followi
I don't have a problem saying something like "we will attempt to
release at least twice per year." I don't think it would be wise to
say, "we will have a release on 1/1 and 7/1 every year."
Release early! Release often! Have 12 releases a year if you want.
Just don't promise them.
On Tue, Mar
Hello,
maybe we could mix both approaches.
Following James, releases could be feature-based, using the JIRA
system. If after 3 months, the goal is reached, we could release.
However, as Gilles suggested we could at least do our best to at least
try and release twice a year. This means that about
As opposed to calendar-based release scheduling, I would suggest
perhaps using a more feature-based approach. For transparency, use
JIRA's target version (or whatever it's called) to schedule which
releases will contain fixes for which issues. The reason I'm hesitant
to put something on the calen
Hi.
> I am -1 to publishing any sort of release schedule to which we would
> be held accountable.
I was speaking for Commons Math. IMHO, it is a disservice to the project to
have releases more than 12 months apart, as it has just been the case.
This gives the feeling that the code is stable and i
I am -1 to publishing any sort of release schedule to which we would
be held accountable.
On Tue, Mar 27, 2012 at 8:33 AM, Gilles Sadowski
wrote:
> Hello.
>
>> > [...]
>> >
>> > But one question I would like to ask is what is the process for
>> > arranging for a new release of Commons-Math. I ask
Hello.
> > [...]
> >
> > But one question I would like to ask is what is the process for
> > arranging for a new release of Commons-Math. I ask because we have
> > 6-month release schedule for our mathematical and utility library, which
> > makes use of Commons Math, and we would like to see whet
Le -10/01/-28163 20:59, Hassan Siddiqui a écrit :
> Dear Commons-Math developers
Hi Hassan,
>
> My name is Hassan Siddiqui and I am working on a Java scientific project
> that involves a significant amount of numerical analysis code. There are
> some 300+ developers and scientist involved in thi
Dear Commons-Math developers
My name is Hassan Siddiqui and I am working on a Java scientific project
that involves a significant amount of numerical analysis code. There are
some 300+ developers and scientist involved in this project.
We are using Commons-Math already to an extent but we do
11 matches
Mail list logo
