We have determined that a BETA release should happen before an RC. This issue will track the progress of the BETA. Does anyone know of an issue that prevents a BETA release?
We have determined that a BETA release should happen before an RC. This issue will track the progress of the BETA. Does anyone know of an issue that prevents a BETA release?
Comments
Comment #1
alliax commentedNo, you can go ahead!
Comment #2
Anonymous (not verified) commented#455678: Remove unnecessary features from xmlsitemap_user
Comment #3
avpaderno#456430: Remove unnecessary features from xmlsitemap_node
#456442: Remove unnecessary features from xmlsitemap_taxonomy
Comment #4
avpadernoI am not sure I understand correctly. Does this list report the issue we should fix before a beta release is released?
What is exactly the plan to go from the actual code, to the first beta release?
Comment #5
alliax commentedJust the strict minimum, something that works just like it used to work before on Drupal5
minimum features, just so that people can install the module and will upgrade in a few months when you'll have time to finish it.
It's just because people would like to have something clear to download and install for D6. At the moment it's pure confusion.
Comment #6
Anonymous (not verified) commentedYes, it should list those issue we feel important to fix before creating a BETA release. It gives reasons why a BETA hasn't occurred.
My goal would be a point in time when there is confirmation that the module is working (I know this is relative) and hard to measure. But once the code proves to provide a sitemap.xml without giving issue we should strike a BETA release.
Comment #7
avpadernoComment #8
fassoni commentedwhere can i find the beta version to test?
Comment #9
avpadernoThere isn't a beta release, yet. The reason of having this report is to list the issue that needs to be resolved, before to create a beta release.
Comment #10
avpadernoThe three issue are almost done.
Comment #11
fassoni commentedOK SORRY.....
THANKS
Comment #12
avpadernoComment #13
Anonymous (not verified) commented#458106: Test for updating from 5.x-1.6 to 6.x-1 has been accomplished.
Comment #14
avpadernoDoes this mean we can release a beta version?
Comment #15
green monkey commentedwell done.... very well done!
going to call you guys "the XML Sitemap cyber swat team" :-)
I don't see RC1 available for download.... different name?
thank you for the push and seeing this through to a release
Comment #16
dave reid@Kiam, earnie: I feel good with tagging a DRUPAL-6--1-0-BETA1 release.
@jwells: We're almost there, but no release is official yet.
Comment #17
green monkey commentedway cool....
google is going to burp.... at least 5 times a day they scan me, looking for this file - I finally get to feed the beast
Comment #18
avpadernoI just created the beta 1 version.
Comment #19
alliax commentedI KISS YOU !!!!! :-)
edit: oh but I'm having a big problem as I'm testing it.. http://drupal.org/node/458546
Comment #20
xmacinfoCongratulations! Beta 1 works like a charm.
My site have only 192 nodes, though. I'll try it on a bigger site later.
Are you planning another beta or going straight to RC?
Comment #21
avpadernoIt's more probably there will be more beta versions, before a release candidate.
Comment #22
dave reidKiam, what do you think about releasing a DRUPAL-6--1-0-BETA2 now that we have the major bugs in beta1 fixed?
Comment #23
avpadernoIn my test site, the cache files are created, but they contain nothing, visiting http://localhost/dr6/sitemap.xml I only obtain a white screen, which is not even an empty sitemap.
The answer is that it's not time for a beta2 version because the problem is far from be resolved.
If anybody is able to find the reason it doesn't work, I will be glad if he shares his knowledge with me. :-)
Comment #24
dave reidSince we now have the beta releases out, I'm marking this a fixed. We can keep track of the critical release issues in #453146: xmlsitemap-6.x-1.0-rc1 Ready, Set, Go.