Re: [Pysparse-users] [Pysparse-developers] Bug from Debian user

[Daniel W. <dan...@gm...>]

Hi,

I did a release of version 1.1 of pysparse, which involved:

  - bumping version number to 1.1
  - creating tags/version-1_1 branch
  - releasing using the tags/version-1_1 branch
  - bumping version number to 1.2a1 (just a way to say that you don't
have version 1,1 but a later revision on trunk)

Future bug fixes should be done on "branches/version-1_1".
"tags/version-1_1" is just a place holder to remember which revision
version 1.1 was, it shouldn't be touched.

There are a lot of changes from 1.0 and I don't know what all of them
are.I think the main difference between 1.1 and 1,0 is the vastly
superior indexing capabilities thanks to Dominque's wonderful effort
to get fancy type indexing working in pysparse.

Cheers

On Wed, Aug 5, 2009 at 3:29 PM, Adam C Powell IV<haz...@de...> wrote:
> On Wed, 2009-08-05 at 15:09 -0400, Daniel Wheeler wrote:
>> On Wed, Aug 5, 2009 at 2:02 PM, Adam C Powell IV<haz...@de...> wrote:
>> > Hi Dan,
>> >
>> > Yes, an official release would be helpful.  Using SVN is generally a
>> > temporary thing, e.g. Elmer is hoping to release 6.0 this Fall, and is a
>> > complex package, so I wanted to use SVN to iron out the bugs before
>> > release.
>>
>> I see. You just need to iron out dependencies and stuff like that
>
> Yeah, that's not a problem.
>
>> > So if there's a 1.1.0 pysparse soon, I'll go ahead and package that.
>>
>> I'll do it soon and give you a heads up when it is done. This is going
>> into the Debian repositories correct? What about Ubuntu?
>
> Yes, into Debian.  Ubuntu slurps Debian packages into their "universe"
> soon after release.  So the Karmic universe is already well-established
> by now, and they'll only update packages if they are core to their
> release plans -- which pysparse almost certainly is not.
>
>> One other thing. Now that pysparse will be in the repositories (and
>> also trilinos in lenny and karmic), I don't think there is anything
>> stopping us going ahead with getting fipy in there. How should I
>> proceed with that?
>
> Indeed, that was my original motivation for packaging PySparse. :-)
>
> I'll revisit that after packaging the new PySparse release.
>
> -Adam
> --
> GPG fingerprint: D54D 1AEE B11C CE9B A02B  C5DD 526F 01E8 564E E4B6
>
> Engineering consulting with open source tools
> http://www.opennovation.com/
>
> ------------------------------------------------------------------------------
> Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
> trial. Simplify your report design, integration and deployment - and focus on
> what you do best, core application coding. Discover what's new with
> Crystal Reports now.  http://p.sf.net/sfu/bobj-july
> _______________________________________________
> Pysparse-developers mailing list
> Pys...@li...
> https://lists.sourceforge.net/lists/listinfo/pysparse-developers
>
>



-- 
Daniel Wheeler