Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Beta/Alpha version release? #1336

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
nacho opened this issue Feb 14, 2013 · 15 comments
Closed

Beta/Alpha version release? #1336

nacho opened this issue Feb 14, 2013 · 15 comments

Comments

@nacho
Copy link
Contributor

nacho commented Feb 14, 2013

Hey,

I guess that you are still a bit far from the stable release, but now that the api is getting stabilized what about a beta release? I ask this 'cause in this way I could start making the package for fedora and maybe other distros. It is also blocking me from making the release for my bindings package.

@linquize
Copy link
Contributor

Will there be 0.18?

@t0xicCode
Copy link

A lot has been added since 0.17, but from what I see, a lot of the features are in development or not fully completed. I do agree that a 0.18 release would be very nice.

@jdavid
Copy link
Member

jdavid commented Apr 9, 2013

+1 for a new release

Me too, this blocks a new release of pygit2. What in turn blocks the very much needed changes to the pygit2 API.

@arrbee
Copy link
Member

arrbee commented Apr 10, 2013

I am very open to a 0.18 release, at this point. We've been hoping, as you know, for a 1.0, but I think there are so many pending changes that we should probably get 0.18 out, accept that it is a disruptive change, and then know that the 0.18 -> 1.0 change will not be as radical (which, in my mind, is actually a good thing).

Some thoughts on what we might want to do prior to an 0.18 tag:

That's probably enough. There are a few other PRs that are worth merging, but I wouldn't consider them release blockers (maybe #1450 and #1459 since they are known pending API changes).

Thoughts?

@nacho
Copy link
Contributor Author

nacho commented Apr 10, 2013

@arrbee why so many things before 0.18? Just release and for each one of those things to be merged make another 0.x release? This will give a lot more testing to the api and to the code itself...

@jdavid
Copy link
Member

jdavid commented Apr 10, 2013

@nacho agree

This is long time overdue. Don't even need to make release notes detailing what has changed since 0.17, just a tag and a tarball, and merging development into master. This would make happy a lot of people.

@arrbee
Copy link
Member

arrbee commented Apr 10, 2013

I only meant to keep the discussion moving, not say that that had to be the list. Those are mostly items where the code is written and are just pending review and merge, but that will have implications for bindings and performance that would be nice to tackle right away. That being said, I was thinking that was a list that was achievable by the end of next week. If it seems longer after discussion, then I agree we shouldn't wait for anything that's more than a couple days of extra work.

@arrbee
Copy link
Member

arrbee commented Apr 10, 2013

Okay, had some offline chat with folks and I think we've got agreement to tag a v0.18.0 release next week.

For reference, a roughly correct current state of things regarding changes from v0.17.0 to the proposed v0.18.0 would be:

Added Externals

  • git_attr_value
  • git_blob_create_fromchunks
  • git_blob_id
  • git_blob_is_binary
  • git_branch_foreach
  • git_branch_is_head
  • git_branch_lookup
  • git_branch_name
  • git_branch_remote_name
  • git_branch_tracking
  • git_branch_tracking_name
  • git_checkout_head
  • git_checkout_index
  • git_checkout_tree
  • git_clone
  • git_commit_nth_gen_ancestor
  • git_config_add_backend
  • git_config_delete_entry
  • git_config_find_xdg
  • git_config_foreach_match
  • git_config_get_entry
  • git_config_lookup_map_value
  • git_config_open_default
  • git_config_open_level
  • git_config_parse_bool
  • git_config_parse_int32
  • git_config_parse_int64
  • git_config_refresh
  • git_cred_userpass
  • git_cred_userpass_plaintext_new
  • git_diff_blob_to_buffer
  • git_diff_find_similar
  • git_diff_get_patch
  • git_diff_num_deltas
  • git_diff_num_deltas_of_type
  • git_diff_patch_delta
  • git_diff_patch_free
  • git_diff_patch_get_hunk
  • git_diff_patch_get_line_in_hunk
  • git_diff_patch_line_stats
  • git_diff_patch_num_hunks
  • git_diff_patch_num_lines_in_hunk
  • git_diff_patch_print
  • git_diff_patch_to_str
  • git_diff_status_char
  • git_graph_ahead_behind
  • git_ignore_add_rule
  • git_ignore_clear_internal_rules
  • git_ignore_path_is_ignored
  • git_index_add_bypath
  • git_index_caps
  • git_index_conflict_add
  • git_index_conflict_cleanup
  • git_index_conflict_get
  • git_index_conflict_remove
  • git_index_get_bypath
  • git_index_has_conflicts
  • git_index_new
  • git_index_owner
  • git_index_remove_bypath
  • git_index_remove_directory
  • git_index_reuc_add
  • git_index_reuc_clear
  • git_index_reuc_entrycount
  • git_index_reuc_find
  • git_index_reuc_get_byindex
  • git_index_reuc_get_bypath
  • git_index_reuc_remove
  • git_index_set_caps
  • git_index_write_tree_to
  • git_libgit2_capabilities
  • git_libgit2_opts
  • git_merge_base_many
  • git_message_prettify
  • git_note_iterator_free
  • git_note_iterator_new
  • git_note_next
  • git_object_peel
  • git_odb_add_disk_alternate
  • git_odb_backend_malloc
  • git_odb_backend_one_pack
  • git_odb_foreach
  • git_odb_refresh
  • git_odb_write_pack
  • git_oid_equal
  • git_oid_fromstrp
  • git_packbuilder_foreach
  • git_packbuilder_free
  • git_packbuilder_insert
  • git_packbuilder_insert_tree
  • git_packbuilder_new
  • git_packbuilder_object_count
  • git_packbuilder_set_threads
  • git_packbuilder_write
  • git_packbuilder_written
  • git_push_add_refspec
  • git_push_finish
  • git_push_free
  • git_push_new
  • git_push_set_options
  • git_push_status_foreach
  • git_push_unpack_ok
  • git_push_update_tips
  • git_refdb_backend_fs
  • git_refdb_compress
  • git_refdb_free
  • git_refdb_new
  • git_refdb_open
  • git_refdb_set_backend
  • git_reference__alloc
  • git_reference_foreach_glob
  • git_reference_has_log
  • git_reference_is_branch
  • git_reference_is_remote
  • git_reference_is_valid_name
  • git_reference_normalize_name
  • git_reference_peel
  • git_reflog_append
  • git_reflog_drop
  • git_refspec_dst_matches
  • git_refspec_force
  • git_refspec_rtransform
  • git_remote_autotag
  • git_remote_check_cert
  • git_remote_is_valid_name
  • git_remote_pushurl
  • git_remote_rename
  • git_remote_set_autotag
  • git_remote_set_callbacks
  • git_remote_set_cred_acquire_cb
  • git_remote_set_pushurl
  • git_remote_set_transport
  • git_remote_set_update_fetchhead
  • git_remote_set_url
  • git_remote_stats
  • git_remote_stop
  • git_remote_update_fetchhead
  • git_repository_detach_head
  • git_repository_fetchhead_foreach
  • git_repository_hashfile
  • git_repository_init_ext
  • git_repository_merge_cleanup
  • git_repository_mergehead_foreach
  • git_repository_message
  • git_repository_message_remove
  • git_repository_refdb
  • git_repository_set_head
  • git_repository_set_head_detached
  • git_repository_set_refdb
  • git_repository_state
  • git_repository_wrap_odb
  • git_reset
  • git_reset_default
  • git_revparse_rangelike
  • git_revparse_single
  • git_revwalk_push_range
  • git_smart_subtransport_git
  • git_smart_subtransport_http
  • git_stash_drop
  • git_stash_foreach
  • git_stash_save
  • git_submodule_add_finalize
  • git_submodule_add_setup
  • git_submodule_add_to_index
  • git_submodule_fetch_recurse_submodules
  • git_submodule_head_id
  • git_submodule_ignore
  • git_submodule_index_id
  • git_submodule_init
  • git_submodule_location
  • git_submodule_name
  • git_submodule_open
  • git_submodule_owner
  • git_submodule_path
  • git_submodule_reload
  • git_submodule_reload_all
  • git_submodule_save
  • git_submodule_set_fetch_recurse_submodules
  • git_submodule_set_ignore
  • git_submodule_set_update
  • git_submodule_set_url
  • git_submodule_status
  • git_submodule_sync
  • git_submodule_update
  • git_submodule_url
  • git_submodule_wd_id
  • git_tag_foreach
  • git_trace_set
  • git_transport_dummy
  • git_transport_local
  • git_transport_new
  • git_transport_smart
  • git_tree_entry_byoid
  • git_tree_entry_bypath
  • git_tree_entry_cmp
  • git_tree_entry_dup
  • git_tree_entry_free
  • git_tree_owner
  • git_treebuilder_entrycount
  • giterr_set_oom
  • giterr_set_str

Removed Externals

  • git_attr__false
  • git_attr__true
  • git_attr__unset
  • git_branch_list
  • git_config_add_file
  • git_config_delete
  • git_config_file__ondisk
  • git_config_open_global
  • git_index_add2
  • git_index_append
  • git_index_append2
  • git_index_entrycount_unmerged
  • git_index_get_unmerged_byindex
  • git_index_get_unmerged_bypath
  • git_index_uniq
  • git_indexer_free
  • git_indexer_hash
  • git_indexer_new
  • git_indexer_run
  • git_indexer_write
  • git_reference_is_packed
  • git_reference_packall
  • git_reference_reload
  • git_tree_get_subtree
  • gitwin_get_codepage
  • gitwin_set_codepage
  • gitwin_set_utf8

Replaced Externals

  • git_blob_create_fromfile -> git_blob_create_fromworkdir
  • git_commit_parent_oid -> git_commit_parent_id
  • git_commit_tree_oid -> git_commit_tree_id
  • git_diff_index_to_tree -> git_diff_tree_to_index
  • git_diff_workdir_to_index -> git_diff_index_to_workdir
  • git_diff_workdir_to_tree -> git_diff_tree_to_workdir
  • git_index_get -> git_index_get_byindex
  • git_reference_create_oid -> git_reference_create
  • git_reference_create_symbolic -> git_reference_symbolic_create
  • git_reference_name_to_oid -> git_reference_name_to_id
  • git_reference_oid -> git_reference_target
  • git_reference_target -> git_reference_symbolic_target
  • git_reference_set_oid -> git_reference_set_target
  • git_reference_set_target -> git_reference_symbolic_set_target
  • git_reflog_entry_msg -> git_reflog_entry_message
  • git_reflog_entry_oidnew -> git_reflog_entry_id_new
  • git_reflog_entry_oidold -> git_reflog_entry_id_old
  • git_remote_new -> git_remote_create_inmemory
  • git_remote_add -> git_remote_create
  • git_tag_target_oid -> git_tag_target_id
  • git_tag_type -> git_tag_target_type
  • git_tree_create_fromindex -> git_index_write_tree
  • git_tree_entry_attributes -> git_tree_entry_filemode

I suspect a couple of further tweaks might go in (for example, if git_revparse_rangelike is renamed to git_revparse) but this is roughly right, I think.

@jdavid
Copy link
Member

jdavid commented Apr 11, 2013

@arrbee That's good news! Thanks.

@nacho
Copy link
Contributor Author

nacho commented Apr 11, 2013

indeed thanks a lot

@carlosmn
Copy link
Member

Another changed external

  • git_branch_tracking -> git_branch_upstream

And an added one

  • git_branch_set_upstream

@arrbee
Copy link
Member

arrbee commented Apr 15, 2013

Just so no one is surprised, we're going to hold off a day before tagging a release. It doesn't seem like a good day for a release.

We did merge a couple of PRs today, so if possible, please look over the head of the development branch and make sure there are no surprises before we tag v0.18 tomorrow.

@vmg
Copy link
Member

vmg commented Apr 16, 2013

And, as promised:

f124ebd

Play around with it. We'll be tagging 1.0preview1 during the Git Merge (11 May) if everything goes according to plan.

@vmg vmg closed this as completed Apr 16, 2013
@jdavid
Copy link
Member

jdavid commented Apr 16, 2013

Thanks, just released pygit2 v0.18.0 and uploaded to pypi.

@t0xicCode
Copy link

I just finished testing the build on my machine and I'll be updating my
ppa to 0.18.0.

On Tue 16 Apr 2013 05:05:25 PM EDT, J. David Ibáñez wrote:

Thanks, just released pygit2 v0.18.0 and uploaded to pypi.


Reply to this email directly or view it on GitHub
#1336 (comment).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants