Lucene development

Steven Rowe (JIRA | 17 Jun 2012 05:17

[jira] [Created] (LUCENE-4150) Change version properties in branch_4x to "4.0-ALPHA-SNAPSHOT"

Steven Rowe created LUCENE-4150:
-----------------------------------

             Summary: Change version properties in branch_4x to "4.0-ALPHA-SNAPSHOT" 
                 Key: LUCENE-4150
                 URL: https://issues.apache.org/jira/browse/LUCENE-4150
             Project: Lucene - Java
          Issue Type: Task
            Reporter: Steven Rowe
            Priority: Minor

The next release off branch_4x will be named "4.0-ALPHA", so the current version string should be "4.0-ALPHA-SNAPSHOT".

(Similarly, after 4.0-ALPHA is released, the version string should be changed to "4.0-BETA-SNAPSHOT".)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

headers

Steven Rowe (JIRA | 17 Jun 2012 05:21

[jira] [Updated] (LUCENE-4150) Change version properties in branch_4x to "4.0-ALPHA-SNAPSHOT"


     [
https://issues.apache.org/jira/browse/LUCENE-4150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Steven Rowe updated LUCENE-4150:
--------------------------------

          Component/s: general/build
          Description: 
The next release off branch_4x will be named "4.0-ALPHA", so the current version string should be "4.0-ALPHA-SNAPSHOT".

(Similarly, after 4.0-ALPHA is released, the version string should be changed to "4.0-BETA-SNAPSHOT".)

  was:
The next release off branch_4x will be named "4.0-ALPHA", so the current version string should be "4.0-ALPHA-SNAPSHOT".

(Similarly, after 4.0-ALPHA is released, the version string should be changed to "4.0-BETA-SNAPSHOT".)

    Affects Version/s: 4.0

Also, shouldn't we have releases 4.0-ALPHA and 4.0-BETA defined in JIRA?

> Change version properties in branch_4x to "4.0-ALPHA-SNAPSHOT" 
> ---------------------------------------------------------------
>
>                 Key: LUCENE-4150
>                 URL: https://issues.apache.org/jira/browse/LUCENE-4150
>             Project: Lucene - Java
>          Issue Type: Task
>          Components: general/build

(Continue reading)

headers

Robert Muir (JIRA | 17 Jun 2012 13:15

[jira] [Commented] (LUCENE-4150) Change version properties in branch_4x to "4.0-ALPHA-SNAPSHOT"


    [
https://issues.apache.org/jira/browse/LUCENE-4150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13393526#comment-13393526
] 

Robert Muir commented on LUCENE-4150:
-------------------------------------

I don't think we should do this. The version logic in e.g. Constants is already insanely scary.
Theres no benefit to making -ALPHA-SNAPSHOT when -ALPHA is already a snapshot. 

{quote}
Also, shouldn't we have releases 4.0-ALPHA and 4.0-BETA defined in JIRA?
{quote}

No. We are targeting 4.0, these are just snapshots of that!

> Change version properties in branch_4x to "4.0-ALPHA-SNAPSHOT" 
> ---------------------------------------------------------------
>
>                 Key: LUCENE-4150
>                 URL: https://issues.apache.org/jira/browse/LUCENE-4150
>             Project: Lucene - Java
>          Issue Type: Task
>          Components: general/build
>    Affects Versions: 4.0
>            Reporter: Steven Rowe
>            Priority: Minor
>
> The next release off branch_4x will be named "4.0-ALPHA", so the current version string should be "4.0-ALPHA-SNAPSHOT".

(Continue reading)

headers

Uwe Schindler (JIRA | 17 Jun 2012 13:25

[jira] [Commented] (LUCENE-4150) Change version properties in branch_4x to "4.0-ALPHA-SNAPSHOT"


    [
https://issues.apache.org/jira/browse/LUCENE-4150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13393529#comment-13393529
] 

Uwe Schindler commented on LUCENE-4150:
---------------------------------------

Since 2.9 releases we never change the version numbers in common-build.xml. This is not done, bacuse when
anybody builds the release from a SVN checkout or a modified local src.tgz extraction, he will not produce
the same artifacts. Because of that we only have the branch name in the default verson string.

When a release is prepared, we explicitely set the version number using -Dversion=foobar.

> Change version properties in branch_4x to "4.0-ALPHA-SNAPSHOT" 
> ---------------------------------------------------------------
>
>                 Key: LUCENE-4150
>                 URL: https://issues.apache.org/jira/browse/LUCENE-4150
>             Project: Lucene - Java
>          Issue Type: Task
>          Components: general/build
>    Affects Versions: 4.0
>            Reporter: Steven Rowe
>            Priority: Minor
>
> The next release off branch_4x will be named "4.0-ALPHA", so the current version string should be "4.0-ALPHA-SNAPSHOT".
> (Similarly, after 4.0-ALPHA is released, the version string should be changed to "4.0-BETA-SNAPSHOT".)

--

(Continue reading)

headers

Uwe Schindler (JIRA | 17 Jun 2012 13:27

[jira] [Comment Edited] (LUCENE-4150) Change version properties in branch_4x to "4.0-ALPHA-SNAPSHOT"


    [
https://issues.apache.org/jira/browse/LUCENE-4150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13393529#comment-13393529
] 

Uwe Schindler edited comment on LUCENE-4150 at 6/17/12 11:26 AM:
-----------------------------------------------------------------

Since 2.9 releases we never change the version numbers in common-build.xml. This is not done, bacuse when
anybody builds the release from a SVN checkout or a modified local src.tgz extraction, he will not produce
the same artifacts. Because of that we only have the branch name in the default verson string.

When a release is prepared, we explicitely set the version number using -Dversion=foobar.

P.S.: This means, when somebody downloads Lucene-3.6.0-src.tgz and then calls ant package, he will get a
-dev/-snapshot build unless he uses -Dversion.

      was (Author: thetaphi):
    Since 2.9 releases we never change the version numbers in common-build.xml. This is not done, bacuse when
anybody builds the release from a SVN checkout or a modified local src.tgz extraction, he will not produce
the same artifacts. Because of that we only have the branch name in the default verson string.

When a release is prepared, we explicitely set the version number using -Dversion=foobar.

> Change version properties in branch_4x to "4.0-ALPHA-SNAPSHOT" 
> ---------------------------------------------------------------
>
>                 Key: LUCENE-4150
>                 URL: https://issues.apache.org/jira/browse/LUCENE-4150
>             Project: Lucene - Java

(Continue reading)

headers

Robert Muir (JIRA | 17 Jun 2012 13:44

[jira] [Commented] (LUCENE-4150) Change version properties in branch_4x to "4.0-ALPHA-SNAPSHOT"


    [
https://issues.apache.org/jira/browse/LUCENE-4150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13393530#comment-13393530
] 

Robert Muir commented on LUCENE-4150:
-------------------------------------

Right, i think its correct now. If someone builds a snapshot, they get 4.0-SNAPSHOT.

to make an alpha release we use -Dversion=4.0-ALPHA.

About jira, after we release i do think we should make the version in JIRA so people
can report bugs against it. But I don't think we should do that now (or people will get
confused about what version to terget things).

The only trick here for alpha/beta is the internal number LUCENE_MAIN_VERSION used
by IndexWriter only internally must be bumped after alpha to 4.0.0.1 or something,
so that we know which exact version of lucene wrote the segment. it must be a number
so that various comparators etc work. but thats totally internal to indexwriter and 
no users see it.

                
> Change version properties in branch_4x to "4.0-ALPHA-SNAPSHOT" 
> ---------------------------------------------------------------
>
>                 Key: LUCENE-4150
>                 URL: https://issues.apache.org/jira/browse/LUCENE-4150
>             Project: Lucene - Java
>          Issue Type: Task

(Continue reading)

headers

Hoss Man (JIRA | 18 Jun 2012 18:21

[jira] [Commented] (LUCENE-4150) Change version properties in branch_4x to "4.0-ALPHA-SNAPSHOT"

[
https://issues.apache.org/jira/browse/LUCENE-4150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13396001#comment-13396001
]

Hoss Man commented on LUCENE-4150:
----------------------------------

bq. About jira, after we release i do think we should make the version in JIRA so people can report bugs
against it. But I don't think we should do that now (or people will get confused about what version to terget things).

Just to be clear, i think this absolutely MUST be done, and would be total chaos otherwise.

If we are going to vote and have official "Alpha" and "Beta" releases that we want end users to actually try
out and test thoroughly, then we are going to need a way to record when a bug was found/fixed in 4.0-Alpha vs
the 4.0-Beta vs the 4.0-final.

Until we have a formally voted on Alpha it's not a big deal, but as soon as that moment happens, ever bug that
currently says "Fixed in: 4.0" should be bulked edited to say "Fixed in: 4.0-Alpha, 4.0" -- so that 9 months
from now when someone says "I'm still running 4.0-Alpha because there was an API change to fix a bug that
made it too hard for me to upgrade to 4.0-Beta" there is a good clean record of what bug fixes they do/don't have.

bq. No. We are targeting 4.0, these are just snapshots of that!

Calling the alpha/beta snapshots is extremely missleading and should be avoided. The only usage of the
term "snapshot" in apache (that i know of) are for *unofficial* nightly/jenkins/svn builds. Since the
alpha/beta releases will in fact be _official_ (VOTEd) releases we should not ever imply/refer to them as
"snapshots" since that would convey lower status on them (and reduce the likely hood of enn users testing
them) then they will deserve.

(Continue reading)

headers

Steven Rowe (JIRA | 18 Jun 2012 20:31

[jira] [Commented] (LUCENE-4150) Change version properties in branch_4x to "4.0-ALPHA-SNAPSHOT"


    [
https://issues.apache.org/jira/browse/LUCENE-4150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13396116#comment-13396116
] 

Steven Rowe commented on LUCENE-4150:
-------------------------------------

I agree with Hoss.

I think 4.0-ALPHA and 4.0-BETA should be full-fledged releases in every way.

> Change version properties in branch_4x to "4.0-ALPHA-SNAPSHOT" 
> ---------------------------------------------------------------
>
>                 Key: LUCENE-4150
>                 URL: https://issues.apache.org/jira/browse/LUCENE-4150
>             Project: Lucene - Java
>          Issue Type: Task
>          Components: general/build
>    Affects Versions: 4.0
>            Reporter: Steven Rowe
>            Priority: Minor
>
> The next release off branch_4x will be named "4.0-ALPHA", so the current version string should be "4.0-ALPHA-SNAPSHOT".
> (Similarly, after 4.0-ALPHA is released, the version string should be changed to "4.0-BETA-SNAPSHOT".)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa

(Continue reading)

headers

Robert Muir (JIRA | 18 Jun 2012 20:47

[jira] [Commented] (LUCENE-4150) Change version properties in branch_4x to "4.0-ALPHA-SNAPSHOT"


    [
https://issues.apache.org/jira/browse/LUCENE-4150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13396129#comment-13396129
] 

Robert Muir commented on LUCENE-4150:
-------------------------------------

Everyone has the right to his own opinion: but for these alpha/betas to me they are snapshots with
additional guarantees: and its better to get them out sooner than later so we can iteratively
incorporate feedback.

If some people want these to be "typical" lucene solr releases each that take months to finish, good for
them, but I strongly disagree (and will not be convinced otherwise!).

Fortunately its ok for us to disagree here, I only need to convince 2 other PMC members for us to get these
things out there: its been way too long for this release.

My advice: if you want these alpha/beta releases to be more solid, get your changes in now because next week I
will spin RCs every 72 hours until we get something out. 

I imagine with enough hassling/bribing it won't be long until 2 other people decide its good to just get the
alpha release out there and get people testing it instead of dragging things out.

                
> Change version properties in branch_4x to "4.0-ALPHA-SNAPSHOT" 
> ---------------------------------------------------------------
>
>                 Key: LUCENE-4150
>                 URL: https://issues.apache.org/jira/browse/LUCENE-4150

(Continue reading)

headers

Mark Miller (JIRA | 19 Jun 2012 15:48

[jira] [Commented] (LUCENE-4150) Change version properties in branch_4x to "4.0-ALPHA-SNAPSHOT"


    [
https://issues.apache.org/jira/browse/LUCENE-4150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13396762#comment-13396762
] 

Mark Miller commented on LUCENE-4150:
-------------------------------------

bq. and will not be convinced otherwise!

I'm glad your open for discussion :)

Personally, I'm not at all concerned about handling these releases as we handle a typical release.

IMHO, snapshot with index back compat attempted promises is the perfect commitment level. Call it a
release, call it a snapshot, I'll vote for either one, but I don't think they should be full fledged
releases at all.

Let's dump this sucker out, and if anyone else wants to pour around some gravy after, so be it.

> Change version properties in branch_4x to "4.0-ALPHA-SNAPSHOT" 
> ---------------------------------------------------------------
>
>                 Key: LUCENE-4150
>                 URL: https://issues.apache.org/jira/browse/LUCENE-4150
>             Project: Lucene - Java
>          Issue Type: Task
>          Components: general/build
>    Affects Versions: 4.0
>            Reporter: Steven Rowe

(Continue reading)

headers

Steven Rowe (JIRA | 19 Jun 2012 16:00

[jira] [Commented] (LUCENE-4150) Change version properties in branch_4x to "4.0-ALPHA-SNAPSHOT"


    [
https://issues.apache.org/jira/browse/LUCENE-4150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13396777#comment-13396777
] 

Steven Rowe commented on LUCENE-4150:
-------------------------------------

By "full fledged" I meant only that these releases should be permanently referable to in all contexts,
unlike snapshots.

> Change version properties in branch_4x to "4.0-ALPHA-SNAPSHOT" 
> ---------------------------------------------------------------
>
>                 Key: LUCENE-4150
>                 URL: https://issues.apache.org/jira/browse/LUCENE-4150
>             Project: Lucene - Java
>          Issue Type: Task
>          Components: general/build
>    Affects Versions: 4.0
>            Reporter: Steven Rowe
>            Priority: Minor
>
> The next release off branch_4x will be named "4.0-ALPHA", so the current version string should be "4.0-ALPHA-SNAPSHOT".
> (Similarly, after 4.0-ALPHA is released, the version string should be changed to "4.0-BETA-SNAPSHOT".)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

(Continue reading)

headers

Steven Rowe (JIRA | 11 Sep 2012 02:34

[jira] [Resolved] (LUCENE-4150) Change version properties in branch_4x to "4.0-ALPHA-SNAPSHOT"


     [
https://issues.apache.org/jira/browse/LUCENE-4150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Steven Rowe resolved LUCENE-4150.
---------------------------------

    Resolution: Won't Fix

> Change version properties in branch_4x to "4.0-ALPHA-SNAPSHOT" 
> ---------------------------------------------------------------
>
>                 Key: LUCENE-4150
>                 URL: https://issues.apache.org/jira/browse/LUCENE-4150
>             Project: Lucene - Core
>          Issue Type: Task
>          Components: general/build
>    Affects Versions: 4.0-ALPHA
>            Reporter: Steven Rowe
>            Priority: Minor
>
> The next release off branch_4x will be named "4.0-ALPHA", so the current version string should be "4.0-ALPHA-SNAPSHOT".
> (Similarly, after 4.0-ALPHA is released, the version string should be changed to "4.0-BETA-SNAPSHOT".)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira