mat-weekly tarball; bzr branches?

Hello,

* As noted in my other post, I have now set up the
"mat-weekly" tarball again.

* Anyone have branches that I should merge from regularly
and/or that should 
be mentioned on the mat website? So far there's just mine in
the list...

Jiri
-- 
Jiri Baum <jiribaum.com.au>                   http://www.baum.com.au/~
jiri

------------------------------------------------------------
-------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the
chance to share your
opinions on IT & business topics through brief
surveys-and earn cash
http://www.techsay.com/default.
php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
MAT-devel mailing list
MAT-devellists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mat-devel

Jiri Baum wrote:
> Hello,
> 
> * As noted in my other post, I have now set up the
"mat-weekly" tarball again.
> 
> * Anyone have branches that I should merge from
regularly and/or that should 
> be mentioned on the mat website? So far there's just
mine in the list...

Hi, I am still around reading the progress of the project
and testing 
some new developments that I want to contribute once I find
the time. I 
am hoping to find some time soon. But of course as an open
source 
project "show me the code" is what rules so
disregard my comment until 
then. I say this because there was some recent concern if
the project 
was alive. From my point of view it is alive and well, it
just lives on 
its own schedule unlike commercial projects there is no rush
or 
deadline. No deadline is a good thing because there is no
time line or 
time schedule that can kill the project if not met 

Now to the point, I am planning to join as an alternative
bzr provider 
for the project. But I have a concern of the data
transmission quota of 
my hosting service.

Is it possible to get first the mat-weekly tarball from
sourceforge and 
then just update to the bzr branch? Is this possible even if
the tarball 
is generated based on your (Jiri's) branch and the update is
done to an 
alternate branch. Of course this procedure will only apply
for the 
initial download. If this is possible it would be desirable
to set this 
as the standard or recommended procedure to download the
project and 
therefore add it to the bzr document manual of the project.

Regards,

Juan Carlos Orozco

> 
> Jiri


------------------------------------------------------------
-------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the
chance to share your
opinions on IT & business topics through brief
surveys-and earn cash
http://www.techsay.com/default.
php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
MAT-devel mailing list
MAT-devellists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mat-devel

Hello,

Juan:
> Is it possible to get first the mat-weekly tarball from
sourceforge and
> then just update to the bzr branch? 

Yes - I would recommend branching off coruscant and then
updating; that has 
the advantage that coruscant shouldn't break  and it'll
almost certainly 
be the ancestor of all the devel branches.

bzr branch http://m
at.sourceforge.net/release/coruscant mat-coruscant
bzr branch mat-coruscant mat-devel
cd mat-devel
bzr pull --remember http://...

This will: (1) get coruscant, (2) make a devel branch for
you and (4) update 
the devel branch to the given URL.

> Of course this procedure will only apply for the
initial download. If this
> is possible it would be desirable to set this as the
standard or recommended
> procedure to download the project and therefore add it
to the bzr document
> manual of the project. 

Yes, I think we should make it the standard.


(Not right now, though... it's after 3am...)

Jiri
-- 
Jiri Baum <jiribaum.com.au>                   http://www.baum.com.au/~
jiri

------------------------------------------------------------
-------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the
chance to share your
opinions on IT & business topics through brief
surveys-and earn cash
http://www.techsay.com/default.
php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
MAT-devel mailing list
MAT-devellists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mat-devel

Jiri Baum wrote:
> Hello,
> 
> Juan:
>> Is it possible to get first the mat-weekly tarball
from sourceforge and
>> then just update to the bzr branch? 
> 
> Yes - I would recommend branching off coruscant and
then updating; that has 
> the advantage that coruscant shouldn't break  and it'll
almost certainly 
> be the ancestor of all the devel branches.
> 
> bzr branch http://m
at.sourceforge.net/release/coruscant mat-coruscant
> bzr branch mat-coruscant mat-devel
> cd mat-devel
> bzr pull --remember http://...
> 
> This will: (1) get coruscant, (2) make a devel branch
for you and (4) update 
> the devel branch to the given URL.


Sounds perfect, exactly what I was looking for.

> 
>> Of course this procedure will only apply for the
initial download. If this
>> is possible it would be desirable to set this as
the standard or recommended
>> procedure to download the project and therefore add
it to the bzr document
>> manual of the project. 
> 
> Yes, I think we should make it the standard.
> 
> 
> (Not right now, though... it's after 3am...)

Of course 

Regards,

Juan Carlos Orozco

> 
> Jiri


------------------------------------------------------------
-------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the
chance to share your
opinions on IT & business topics through brief
surveys-and earn cash
http://www.techsay.com/default.
php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
MAT-devel mailing list
MAT-devellists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mat-devel

Jiri Baum wrote:
> Hello,
> 
> Juan:
>> Is it possible to get first the mat-weekly tarball
from sourceforge and
>> then just update to the bzr branch? 
> 
> Yes - I would recommend branching off coruscant and
then updating; that has 
> the advantage that coruscant shouldn't break  and it'll
almost certainly 
> be the ancestor of all the devel branches.
> 
> bzr branch http://m
at.sourceforge.net/release/coruscant mat-coruscant
> bzr branch mat-coruscant mat-devel
> cd mat-devel
> bzr pull --remember http://...
> 
> This will: (1) get coruscant, (2) make a devel branch
for you and (4) update 
> the devel branch to the given URL.
> 
>> Of course this procedure will only apply for the
initial download. If this
>> is possible it would be desirable to set this as
the standard or recommended
>> procedure to download the project and therefore add
it to the bzr document
>> manual of the project. 
> 
> Yes, I think we should make it the standard.

OK, my main branch is now up. http://www.acelab.c
om/mat/mat-ace

Right now it is basically coruscant and then a pull from
your (Jiri's) 
main branch.

I will start to commit some work to this branch. I will let
the list 
know of any updates.

Regards,

Juan Carlos Orozco

> 
> 
> (Not right now, though... it's after 3am...)
> 
> Jiri


------------------------------------------------------------
-------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and
take
control of your XML. No limits. Just data. Click to get it
now.
http://sourcefor
ge.net/powerbar/db2/
_______________________________________________
MAT-devel mailing list
MAT-devellists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mat-devel