Re: [ jEdit-devel ] 4.4.1?

[Matthieu C. <cho...@gm...>]

Hi,
so about releasing I understand our objective is now to do only stable
releases.
Relatively often for the current stable release depending on merges that are
done, and on a schedule for more important releases.
Having a roadmap is a good idea, but not easy to do for two main reasons.
First I don't think two developpers can implement the same feature together,
it would be too complicated.
Second, nobody is working full time on jEdit so nobody can say he will
finish a big task for a given date.

So maybe we can have in a roadmap the list of wanted features (I mean
important features, not microfeatures), and when a developper have time he
can start implementation of one of them.

In fact I started some sort of roadmap on the wiki, but I don't find it
anymore (I mean the sourceforge's wiki), does anyone knows where it is now ?

Matthieu

2010/3/18 Kazutoshi Satoda <k_s...@f2...>

> Eric Berry wrote:
> > On Wed, Mar 17, 2010 at 11:01 AM, Kazutoshi Satoda
> > <k_s...@f2...>wrote:
> >>  Yes, because I think 4.3.2 is far more important for majority of users,
> >>  than 4.4.0 which might be more interesting for developers.
> >
> > I'm not sure we can say this one for certain. I haven't read the
> changes.txt
> > file yet, but I'm sure there are new features on there that Users would
> like
> > to have, otherwise I don't think people would have made the changes.
>
> I'll post a call for votes to prioritize development tasks. This can be
> a concrete base of our future decisions. I'll try hard to hide my bias
> tempted to prioritize the 4.3.x line.
>
> I tried to start using SourceForge.net hosted app, LimeSurvey, for this.
> But I gave up after 10 minutes learning it, only because of my laziness.
> FYI, it has been just enabled. It's OK if anyone present concrete use
> of this app.
> https://sourceforge.net/apps/limesurvey/jedit/
>
> > Cool. Then we should copy over the stuff from the changes.txt which has
> been
> > added since the 4.3 release to the 4.4.0 future release plan.
>
> Copy to what? I think you don't need to do. I think only the explicit
> requirements should be listed, and that's enough.
>
> >>   "1. Define a set of requirements for the next stable release."
> (snip)
> > Anyone have a good idea of where to do this? It needs to be public, and
> if
> > there was some way users could vote on features it would be very useful.
> > I've thought about using the Wiki, but I don't know if users are using it
> > frequently. Perhaps a thread on jEdit-users list?
>
> It might also bubble up from the above call for votes.
>
> >>  Now I realized that we need to have a way to release accumulated minor
> >>  improvements.
> >>
> >>  I think adding a time based rule is a solution. Like this:
> >>  If 6 months passed from the last branching (step 3) during step 1,
> >>  then step 1 and 2 can be skipped assuming the major requirement is
> >>  "make a new stable release".
> >
> > Awesome, I think this will help a lot.
>
> I'll follow your discussion about the actual span for this kind of
> rule.
>
> --
> k_satoda
>
>
> ------------------------------------------------------------------------------
> Download Intel&#174; Parallel Studio Eval
> Try the new software tools for yourself. Speed compiling, find bugs
> proactively, and fine-tune applications for parallel performance.
> See why Intel Parallel Studio got high marks during beta.
> http://p.sf.net/sfu/intel-sw-dev
> --
> -----------------------------------------------
> jEdit Developers' List
> jEd...@li...
> https://lists.sourceforge.net/lists/listinfo/jedit-devel
>