Freshmeat.net page not up to date

[Jari Aalto]

Many follow the Freshmeat Open Source HUB to receive release announcements and news. The nice thing about the Freshmeat is that it has very easy and simple subscribe functionality to announcements; and you can browse other interesting related projects from one place.

It appears that this page is quite a bit behind:

   http://freshmeat.net/projects/bzr

If possible, it would be nice if announcements about official releases were alo sent to that page.

Thanks,
Jari

[Martin Pool (mbp)]

Thanks for pointing that out.

Vincent, our release manager, should now have access. I've also turned on the "anyone can make (reviewed) edits" flag. I'll let Vincent actually add the changes to make sure that it's working for him.

[Vincent Ladeuil (vila)]

I've submitted some changes to the page which are currently under verification (they say this should take less than 24 hours).

Since the submissions are timestamped, there was no way I could see to document the releases made since 2.1.0b4, so I settled with announcing 2.2.2 which is our latest stable release and will make another submission for 2.3b4.

It seems that all URLs defined when creating a release are unique so only the latest we define are published on freshmeat (even if you try to drill down to a specific release).

Our releasing.txt document says to announce the betas there which means people wont be able to get the latest stable...

Oh well, there are enough links to launchpad to get there I think.

@Jari: what's your expectation when going to freshmeat ? latest stable or most recent (aka beta) ?

[Jari Aalto (jari-aalto)]

> I've submitted some changes to the page which are currently under
> verification (they say this should take less than 24 hours).

Thanks for quick heads up.

> @Jari: what's your expectation when going to freshmeat ? latest stable
> or most recent (aka beta) ?

Announcing stable version at Freshmeat is enough.

While we're at, could you also:

1. Add new link to the right: point "Download" to Launchpad betas download page
2. Add new link to the right: "Devel releases" to point to betas.
3. Fix "tar/gz" link. Intead of pointing directly to file, point it to stable download page.

Thanks,
Jari

[Vincent Ladeuil (vila)]

>>>>> Jari Aalto <email address hidden> writes:

    >> I've submitted some changes to the page which are currently under
    >> verification (they say this should take less than 24 hours).

    > Thanks for quick heads up.

    >> @Jari: what's your expectation when going to freshmeat ? latest stable
    >> or most recent (aka beta) ?

    > Announcing stable version at Freshmeat is enough.

    > While we're at, could you also:

    > 1. Add new link to the right: point "Download" to Launchpad betas download page

Assuming you mean stable not beta here.

    > 2. Add new link to the right: "Devel releases" to point to betas.
    > 3. Fix "tar/gz" link. Intead of pointing directly to file, point it to stable download page.

Done (with tweaks).

So I went with the idea that users should be pointed to the latest
stable release by default. More adventurous ones can find the betas or
the bazaar branch, I'll update our releasing.txt accordingly and will
submit a merge proposal for that.

--23CBD180AF0.1292574971/axe--

[Vincent Ladeuil (vila)]

    > Announcing stable version at Freshmeat is enough.

    > While we're at, could you also:

    > 1. Add new link to the right: point "Download" to Launchpad betas download page

Assuming you mean stable not beta here.

    > 2. Add new link to the right: "Devel releases" to point to betas.
    > 3. Fix "tar/gz" link. Intead of pointing directly to file, point it to stable download page.

Done (with tweaks).

So I went with the idea that users should be pointed to the latest stable release by default. More adventurous ones can find the betas or the bazaar branch, I'll update our releasing.txt accordingly and will submit a merge proposal for that.

[Jari Aalto (jari-aalto)]

| > 1. Add new link to the right: point "Download"
|
| Assuming you mean stable not beta here.

Yes

| > 2. Add new link to the right: "Devel releases" to point to betas.
| > 3. Fix "tar/gz" link. Intead of pointing directly to file, point it to stable download page.
|
| So I went with the idea that users should be pointed to the latest
| stable release by default. More adventurous ones can find the betas or
| the bazaar branch, I'll update our releasing.txt accordingly and will
| submit a merge proposal for that.

Exactly my thoughts

Thanks,
Jari

[Vincent Ladeuil (vila)]

So, unfortunately freshmeat doesn't agree with us about the distinction between stable and devs releases.

Their policy (and UI) discourage using announcements for dev releases:

  Please do not use announcements for new versions of your software! Submit a new release instead.

And 'Submit new release' ask for URLs for the Links box, so there is no way to announce dev releases with the proper URLs while keeping the stable URLs in this box.

It also seems that they re-order my last submission and the 'bzr branch' is still the first one in the 'Links' box...

I'm getting in touch with them to sort this out, my tweaks to the releasing.txt have landed so there is a slight incoherence so far, no big deal.

I'll leave the bug open in the meant time.

[Jari Aalto (jari-aalto)]

| So, unfortunately freshmeat doesn't agree with us about the
| distinction between stable and devs releases. Their policy (and
| UI) discourage using announcements for dev releases:
|
| Please do not use announcements for new versions of your
| software! Submit a new release instead.

I think it is good enough to have only stable announcements at
Freshmeat. Less management. Those who interested in betas, can
access them from the right hand.

Thanks,
Jari

[Vincent Ladeuil (vila)]

@Jari: Thanks !

That's my feeling too, I'm discussing with freshmeat right now but I think we will end up with adding an URL for the latest beta and announce only stable releases.

As an additional weak point there, the URLs are sorted alphabetically on their labels, which is why the 'Website' comes last and the Bazaar Branch first... almost the exact opposite of what I wanted...

[Vincent Ladeuil (vila)]

I've revised the URLs labels which should now address our needs (and we can still announce betas ;)