Arttu Manninen wrote:
Henri Bergius to Andreas Flack
I ran pear upgrade-all today which upgraded n.n.blog to 1.3.0beta2, which
produces lots of notices like Undefined variable: data. the stability
for the
package is set to "stable", but it should be "beta" as far as i can tell.
Agreed, it should be marked "beta" instead of stable.
This is my bad. I was comparing all the files and backported plenty of
new for the old releases. `manifest.inc` had wrong stability, since due
to someone's badly made script (I presume, since all the manifests had
the same in trunk all the sudden were very badly formatted) I copied and
pasted it from a place I had already been reformatting it.
I changed the version number, but not the stability.
But the actual issue is that $data array loading was changed between
2.6 and 2.8, and 1.3.0beta2 really needs MidCOM 2.8 but that doesn't
seem to be in package dependencies.
I'd say that a longer-lasting solution would be to release a MidCOM
2.6.3 with `$data` fix. There are anyways some issues with the current
stable MidCOM and we can't only speed up in the future and let the
bridges break behind.
Arttu, can you fix and re-upload?
I will do this first thing tomorrow morning. I deleted now the wrong
release.
Ah, changing the stability could be so much easier. I'll add this to the
TODO list of MidCOM PEAR server, which is slowly starting to shape up.
Some of the features I plan to include are
* Pending releases
- If user doesn't have (yet) privileges to create a new release
it will be pending for an approval; a message will be sent to
the package lead
* Counter
- We could get to know how many and what versions of packages are in
use
* Changelog
- Using the documentation/CHANGES file I could parse a changelog;
using SVN commit notes might be a bad idea, since they can be very
varying and not for the greater public any way - especially when
developing a new component or major features
What would be smart is if we moved the CHANGES file to xml and then had
some phing commands to manipulate it so that when you do phing package
they just get included as the changelog entries in package.xml. Also,
phing package should have an extra comment usage for adding an extra
comment when uploading the file.
something like:
%>phing -Dmodule=net.nehmer.blog comment
Write comment:
Changed the rss system to use RSS 3.0 ^d
%>
Another idea is to add a set of keywords to the svn comments:
CHANGE: functionlity change ,
API: for api changes
, and
DB: For changes requireing changes in the db.
There were also some other ideas I wrote down, but I left my laptop in
the office so that I wouldn't work at home. ;)
My biggest wish:
Commandline upload of new releases.
Regards,
Tarjei
_______________________________________________
user mailing list
[email protected]
http://lists.midgard-project.org/mailman/listinfo/user
