[development] releases, recommended/supported changing automatically on release creation...
Darrel O'Pry
darrel.opry at gmail.com
Mon Mar 10 18:42:16 UTC 2008
well filefield 2.2 (I can only specify major version on the releases
page) is recommended and supported, but it seems to be branch specific,
not release specific...
I find a lot of the terminology and workflow around the new release
system very confusing...
ala...
supported I don't think is a good word... It implies more than I want it
to... like my dev and rc releases aren't 'supported', but they're
maintained, and I want them displayed for the brave who want to test
them, but I don't want to commit myself to supporting them. It's a
question of managing expectations as the user community grows.
I'm also really confused about why we tie releases to branches and not
the release nodes.... I want to set releases to supported or
recommended... not branches of my code... branches are not synonymous to
releases...
my hungover thoughts this morning...
.darrel.
On Sun, 2008-03-09 at 15:22 -0500, Khalid Baheyeldin wrote:
> Daryl
>
> Check here http://drupal.org/node/72560/edit/releases
>
> See if you can tweak "supported" and "recommended" to do what you
> want.
>
> On Sun, Mar 9, 2008 at 3:01 PM, Darrel O'Pry <darrel.opry at gmail.com>
> wrote:
> So today I'm humming a long and create a new RC for imagefield
> 2.3.. I
> go back to the project page, and wow the RC is the recommended
> and
> supported version listed there... Totally not cool! How many
> people are
> going to that when they should be using the 2.2 release,
> thanks to
> update_status.module. I think it is really bad to
> automatically change
> these flags on maintainers. I think it should be left to the
> maintainer
> to decide when a release is recommended or supported.
>
> .darrel.
>
>
>
>
> --
> Khalid M. Baheyeldin
> 2bits.com, Inc.
> http://2bits.com
> Drupal optimization, development, customization and consulting.
More information about the development
mailing list