Hi,
so what remains todo befor 6.4rc1? IMO lib API and module list should be
frozen at that point, which means creating releasebranch_6_4. No need to
wait on that anymore IMO. bugfixes can continue on until the end.
if 6.4 is the last, that means for all of GRASS 6.x so last chances...
http://gra
Hi,
I'm following a bit GRASS 7 development via trac timeline and for me
GRASS 7.0 seems to be yet far, far away. Taking into account our
development speed, it seems more like 1-2 years till final stable
release. Unless magic happens and we get bunch of some die-hard
programmes that address all v/r
On Mon, Dec 1, 2008 at 10:09 AM, Hamish <[EMAIL PROTECTED]> wrote:
> Hi,
>
> so what remains todo befor 6.4rc1? IMO lib API and module list should be
> frozen at that point, which means creating releasebranch_6_4. No need to
> wait on that anymore IMO. bugfixes can continue on until the end.
> if 6
Hi,
2008/12/1 Hamish <[EMAIL PROTECTED]>:
> so what remains todo befor 6.4rc1? IMO lib API and module list should be
> frozen at that point, which means creating releasebranch_6_4. No need to
> wait on that anymore IMO. bugfixes can continue on until the end.
> if 6.4 is the last, that means for a
Hi,
2008/12/1 Hamish <[EMAIL PROTECTED]>:
> so what remains todo befor 6.4rc1? IMO lib API and module list should be
> frozen at that point, which means creating releasebranch_6_4. No need to
I also added to the list nviz_cmd module. I am not sure about its
name. Any ideas?
nviz.cmd
?
Martin
On Mon, 1 Dec 2008, Martin Landa wrote:
Hi,
2008/12/1 Hamish <[EMAIL PROTECTED]>:
so what remains todo befor 6.4rc1? IMO lib API and module list should be
frozen at that point, which means creating releasebranch_6_4. No need to
I also added to the list nviz_cmd module. I am not sure about it
On Dec 1, 2008, at 9:42 AM, Paul Kelly wrote:
On Mon, 1 Dec 2008, Martin Landa wrote:
Hi,
2008/12/1 Hamish <[EMAIL PROTECTED]>:
so what remains todo befor 6.4rc1? IMO lib API and module list
should be
frozen at that point, which means creating releasebranch_6_4. No
need to
I also added
On Mon, Dec 1, 2008 at 3:44 PM, Helena Mitasova <[EMAIL PROTECTED]> wrote:
> On Dec 1, 2008, at 9:42 AM, Paul Kelly wrote:
>> On Mon, 1 Dec 2008, Martin Landa wrote:
>>> I also added to the list nviz_cmd module. I am not sure about its
>>> name. Any ideas?
>>>
>>> nviz.cmd
>>
>> What about reviving
Martin Landa wrote:
> I also vote for creating releasebranch_6_4 within the next
> days...
>
> what about
>
> http://trac.osgeo.org/grass/ticket/72
> It would be also good to make wx digitizer working under MS Windows.
> Any winGRASS power users for testing wxGUI?
yes
> and
> http://trac.o
Maris Nartiss wrote:
> I'm following a bit GRASS 7 development via trac timeline and for me
> GRASS 7.0 seems to be yet far, far away. Taking into account our
> development speed, it seems more like 1-2 years till final stable
> release. Unless magic happens and we get bunch of some die-hard
> pr
Martin Landa wrote:
> > so what remains todo befor 6.4rc1? IMO lib API and module list should be
> > frozen at that point, which means creating releasebranch_6_4. No need to
> > wait on that anymore IMO. bugfixes can continue on until the end.
> > if 6.4 is the last, that means for all of GRASS 6
Paul Kelly wrote:
> >> so what remains todo befor 6.4rc1? IMO lib API and module list should be
> >> frozen at that point, which means creating releasebranch_6_4. No need to
> >
> > I also added to the list nviz_cmd module. I am not sure about its
> > name. Any ideas?
> >
> > nviz.cmd
>
> What a
Glynn Clements wrote:
> > > so what remains todo befor 6.4rc1? IMO lib API and module list should be
> > > frozen at that point, which means creating releasebranch_6_4. No need to
> > > wait on that anymore IMO. bugfixes can continue on until the end.
> > > if 6.4 is the last, that means for all
> > http://grass.osgeo.org/wiki/GRASS_6.4_Feature_Plan
> >* d.frame.split?
> >* r.colors.stddev?
> >* v.colors?
>
> Yes, please v.colors - no opinion on the others.
I added them all.
d.frame.split: added as d.split.frame in 6.4 (only) as a replacement to
d.split. (for posterity's sa
Hi,
2008/12/1 Martin Landa :
> 2008/12/1 Hamish :
>> so what remains todo befor 6.4rc1? IMO lib API and module list should be
>> frozen at that point, which means creating releasebranch_6_4. No need to
>
> I also added to the list nviz_cmd module. I am not sure about its
> name. Any ideas?
>
> nvi
On Thu, 18 Dec 2008, Martin Landa wrote:
Hi,
2008/12/1 Martin Landa :
2008/12/1 Hamish :
so what remains todo befor 6.4rc1? IMO lib API and module list should be
frozen at that point, which means creating releasebranch_6_4. No need to
I also added to the list nviz_cmd module. I am not sure
Martin wrote:
> > I also added to the list nviz_cmd module. I am not
> > sure about its name. Any ideas?
> >
> > nviz.cmd
>
> I remember votes for d.3d and votes again this proposal.
> Any consensus before rc1?
my 0c vote is for d.3d [for the d.* purists: could the outputted png be
used in the GU
Hamish wrote:
> > > I also added to the list nviz_cmd module. I am not
> > > sure about its name. Any ideas?
> > >
> > > nviz.cmd
> >
> > I remember votes for d.3d and votes again this proposal.
> > Any consensus before rc1?
>
> my 0c vote is for d.3d [for the d.* purists: could the outputted p
ML:
> >>> I also added to the list nviz_cmd module. I am not sure about its
> >>> name. Any ideas?
> >>> nviz.cmd
PK:
> >> What about reviving the d.3d name? Or something that makes the
> >> functionality more obvious than nviz.cmd? I kind of think it should
> >> be a d.* command because it is real
19 matches
Mail list logo
