It's not in SVN yet. I'm using git right now. I'll let you all know when
it's up somewhere!
Just want to add that I really don't want to make any enemies because of
the 1.3.0 release. It would have been entirely ok with me if it just was
clear that I wasn't the only developer. I am rather picky about testing,
but I'm definitely not angry with anyone for releasing too early. All
software has bugs. Updating the info about who created the application
is easy to miss too, although important (people will expect the sole
creator to be responsible for its quality).
Good with volonteers for testing alpha/beta/RC builds. I will happily
test things too. Just let me know.
Regards,
Hampus
Bram Neijt skrev 2010-03-13 13:05:
Release early, release often ;)
Don't forget to put your code in the SVN so I check it out and
possibly help with it. Or is it in there somewhere already?
I still have to work on the metalinkvalidator, so I have not really
got time left for other stuff, but if you post the code and I have a
minute left, I may be able to comment.
The problem with 1.3.0 doesn't seem that severe, but if you are
working on a C++ replacement, it is porbably best. We should also see
if it would be a good idea to incorporate our efforts in a more
complete program.. somebody should check that.
Lastly, a alpha/beta/release-candidate should be no problem. Let me
know when it's up for testing :)
Bram
On Sat, Mar 13, 2010 at 11:58 AM, Hampus Wessman
<[email protected]> wrote:
I just removed the Metalink Editor 1.3.0 release from sourceforge.net. It
has at least one severe bug and states me as the only developer. Not good.
No hard feelings, but it's important for me that software with my name on it
works flawlessly (or contains bugs created by me). I think this is the best
solution for now.
If we want to create a new release (e.g. 1.3.1) of the python metalink
editor, I think we should change all information about the authorship so
that it's clear that I'm not responsible for all of the current source code
(and to give credit to everyone involved). We should also fix all bugs of
course. Right now it fails to save meta4-files (complains about a comparison
between an integer and a string). Some prior testing would probably be good
(like a release candidate).
I'm currently working on my new C++ Metalink Editor (finally have some time
for that!). Expect to hear more about that soon, once I've gotten somewhere
with it.
/ Hampus
Neil M. skrev 2010-02-28 01:12:
I just made releases of the following software that should be up to date
with the v28 approved RFC draft. Ant already included the URL for web
conversion service, the other two products can be downloaded from the
sourceforge website:
- Web Conversion Service
- Metalink Checker
- Metalink Editor
https://sourceforge.net/projects/metalinks/files/
Neil
On 2/27/2010 12:00 PM, Anthony Bryan wrote:
our Internet Draft/RFC appears to be done. now comes the fun part :)
there is quite a lot of software out there that supports metalink3.
here's what supports metalink4:
http://groups.google.com/group/metalink-discussion/web/internetdraft
aria2 (patch, ready for 1.9.0)
KGet?
metalink checker (used by GGet, which Neil has ported to Windows)
metalink editor
Neil's web converter (
http://www.nabber.org/projects/metalink/webconvert/ )
(note that all these probably need to be updated to the latest -28
draft, we changed a few names like<metaurl mediatype=""> (from
<metaurl type="">)& maybe something else since these were
implemented)
Peter is working on it for MirrorBrain. it'll nice to be test it out
with aria2/checker.
what other metalink enabled apps should we focus on short/mid term?
probably the generating apps, so people have a way to make the new
metalinks...
Bram's metalink tools?
libmetalink?
metalink-library?
--
You received this message because you are subscribed to the Google Groups
"Metalink Discussion" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/metalink-discussion?hl=en.
--
You received this message because you are subscribed to the Google Groups "Metalink
Discussion" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/metalink-discussion?hl=en.
