Hey there, this module is used by drupal.org, and as part of the https://drupal.org/community-initiatives/drupalorg/drupal7 D7 Upgrade Initiative, we need to get it to a stable 1.0 release prior to launch.

What will it take to get a release of this module out the door before July 15th, 2012 so we can test it in-place during the QA phase? Let's use this issue to investigate and generate a bullet-point list of things that need to happen (or a list of links to other issues).

Comments

senpai’s picture

senpai commented
Issue tags: +drupal.org D7, +porting

Tagging.

kssundar’s picture

kssundar commented
Status: Active » Needs review

Please provide information on what fixes/tasks has to be done in order to create a stable release.

c-logemann’s picture

c-logemann
he/him
Primary language German
Location Frankfurt/M, Germany
commented
Assigned: Unassigned » c-logemann

This module is not very complex and there are no open bug issues only feature requests. So it seems that it is very stable.

I suggest the following strategy:
First I will do some little tests of current dev version in the next days and will release a beta version if I find no problem.
I hope this will bring some attention to beta testing. I feel better to make a stable release if some people giving positive feedback instead of just thinking there are no bugs left. This can be done with comments in this issue. Giving me a positive feedback can be started also with the current dev release ...

c-logemann’s picture

c-logemann
he/him
Primary language German
Location Frankfurt/M, Germany
commented
Version: 7.x-1.0-alpha1 » 7.x-1.x-dev

Just changed the version.

kssundar’s picture

kssundar commented

I put my observations here #1722084: Need clarification on how uniqueness of a machine name is considered in this module

c-logemann’s picture

c-logemann
he/him
Primary language German
Location Frankfurt/M, Germany
commented

As I wrote "This can be done with comments in this issue" I meant that reporting "everything OK" can be done with a comment here.

@ksbalajisundar: You are talking about possible problems you see and by default it's a bug in my opinion. So it's better to discuss your "review" in an own issue. Please open a new issue and move your "szenario descriptions". Then you can just leave a link in your comment here when you editing it.

senpai’s picture

senpai commented
Version: 7.x-1.x-dev » 7.x-1.0-alpha1
Assigned: c-logemann » Unassigned

Just a reminder: Final QA starts next week, and I'd hate it if this module wasn't ready and we had to put a hold on the entirety of the drupal.org D7 upgrade.

senpai’s picture

senpai commented
Assigned: Unassigned » senpai
Priority: Major » Critical

Elevating this one to critical because the drupal.org functionally complete deadline is the end of this month.

c-logemann’s picture

c-logemann
he/him
Primary language German
Location Frankfurt/M, Germany
commented

As I understand the original maintainers built a contrib module instead of a custom solution for something they needed for d.o in future (the project module). But now this module is living in the contrib world with feature requests and bugs/problemes outside the needs of d.o.

Maybe somebody of the D7 Upgrade Initiative can give some feedback of testing the module in the d.o context. Which Version are the D7 Upgrade Initiative testing right now? The old alpha or the current dev version? Because you have marked this issue again with the alpha version you mean possibly this?

What should I do now? I can make "special d.o stable version" 7.1 based on the alpha version or which code base you are testing with success. There is only a need of special documentation about limits outside this context. Then I can move all the new development and bugfixing to a new branch 7.2. Is this fitting your needs?

adamdicarlo’s picture

adamdicarlo commented

Yes, please roll a 7.x-1.0 release for machine name and work on new development in a 7.x-2.x branch.

greggles’s picture

greggles
he/him
Primary language English
Location Denver, Colorado, USA
commented

@adamdicarlo - should that 7.x-1.0 be the same code as 7.x-1.0-alpha or should it be the latest in the 7.x-1.x branch?

senpai’s picture

senpai commented

@greggles, we're running 7.x-1.0-alpha1+4-dev on the canonical D7 staging server right now, but what does that version string even mean?

adamdicarlo’s picture

adamdicarlo commented

@greggles, @C_Logemann - we want want what's on the canonical D7 staging server, so 7.x-1.0-alpha1+4-dev.

As I understand it, that means 4 commits ahead of the 7.x-1.0-alpha1 tag. Looks like that's the very latest commit to the project (on the 7.x-1.x branch at least): e0da251e.

So - please roll off of HEAD!

c-logemann’s picture

c-logemann
he/him
Primary language German
Location Frankfurt/M, Germany
commented

Ok, I will add and fill the missing README.txt file and maybe do some code cleanup but will not change any functions. Then I will create a stable release.

c-logemann’s picture

c-logemann
he/him
Primary language German
Location Frankfurt/M, Germany
commented

I have added README.txt and did a little bit code cleanup:
http://drupalcode.org/project/machine_name.git/commit/6fc66e7
http://drupalcode.org/project/machine_name.git/commit/8960a46

I will wait with stable because of #1822252: Allow machine_name to provide field indexing to ApacheSolr

senpai’s picture

senpai commented

@C_Logemann, ready to rock n' roll a stable release now, yeah?

c-logemann’s picture

c-logemann
he/him
Primary language German
Location Frankfurt/M, Germany
commented
Status: Needs review » Active

The ApacheSolr patch is committed and this codebase tagged as stable 7.x-1.0:
http://drupalcode.org/project/machine_name.git/shortlog/refs/tags/7.x-1.0
Now I am waiting for d.o update to initiate release creation.

c-logemann’s picture

c-logemann
he/him
Primary language German
Location Frankfurt/M, Germany
commented

I just found a new Issue about "Search API on Drupal.org" is this a release blocker close to the goal?
#1832328: Expose Entity Metadata property (for Search API, etc.)

kscheirer’s picture

kscheirer
Primary language English
Location Vallejo
commented
Status: Active » Reviewed & tested by the community

Your tag should have been published by now, did you make a new release node? From the project homepage you should be able to click "Administer releases" and make it official.

#1832328: Expose Entity Metadata property (for Search API, etc.) has a patch ready to go too, so either way I think this issue is done.

greggles’s picture

greggles
he/him
Primary language English
Location Denver, Colorado, USA
commented

Yes, it's available on http://drupal.org/node/add/project-release/1320352

c-logemann’s picture

c-logemann
he/him
Primary language German
Location Frankfurt/M, Germany
commented

@greggles, @kscheirer: I know how to create this.

@D7 Upgrade Initiative: I'm waiting for answers of my question in comment #18

If #1832328: Expose Entity Metadata property (for Search API, etc.) is needed for the special "d.o upgrade release" I want to tag as 7-x.1.1 and publish this as official stable release.

greggles’s picture

greggles
he/him
Primary language English
Location Denver, Colorado, USA
commented

@C_Logemann, given that #1832328: Expose Entity Metadata property (for Search API, etc.) was tagged for something related to drupal.org I'd say it's somewhat important. However, in the absense of a concrete answer I suggest this:

1. Create a stable 7.x-1.0 release of the code without that.
2. Wait and get an answer, or just commit that and push it in the 7.x-1.1 whenever you have time for it.

c-logemann’s picture

c-logemann
he/him
Primary language German
Location Frankfurt/M, Germany
commented
Version: 7.x-1.0-alpha1 » 7.x-1.0
Status: Reviewed & tested by the community » Fixed

The Release is created: http://drupal.org/node/1841996

Automatically closed -- issue fixed for 2 weeks with no activity.